draft-ietf-softwire-ds-lite-tunnel-option-09.txt   draft-ietf-softwire-ds-lite-tunnel-option-10.txt 
Softwire D. Hankins Softwire D. Hankins
Internet-Draft Google Internet-Draft Google
Intended status: Standards Track T. Mrugalski Intended status: Standards Track T. Mrugalski
Expires: September 4, 2011 Gdansk University of Technology Expires: September 8, 2011 Gdansk University of Technology
March 3, 2011 March 7, 2011
Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual- Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual-
Stack Lite Stack Lite
draft-ietf-softwire-ds-lite-tunnel-option-09 draft-ietf-softwire-ds-lite-tunnel-option-10
Abstract Abstract
This document specifies a DHCPv6 option which is meant to be used by This document specifies a DHCPv6 option which is meant to be used by
a Dual-Stack Lite Basic Bridging Broadband (B4) element to discover a Dual-Stack Lite Basic Bridging Broadband (B4) element to discover
the IPv6 address of its corresponding Address Family Transition the IPv6 address of its corresponding Address Family Transition
Router (AFTR). Router (AFTR).
Status of this Memo Status of this Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 4, 2011. This Internet-Draft will expire on September 8, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 14 skipping to change at page 2, line 14
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Requirements Language . . . . . . . . . . . . . . . . . . . . . 3 1. Requirements Language . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. The AFTR-Name DHCPv6 Option . . . . . . . . . . . . . . . . . . 3 3. The AFTR-Name DHCPv6 Option . . . . . . . . . . . . . . . . . . 3
4. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . . . . 5 4. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . . . . 5
5. DHCPv6 Client Behavior . . . . . . . . . . . . . . . . . . . . 5 5. DHCPv6 Client Behavior . . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7
9. Normative References . . . . . . . . . . . . . . . . . . . . . 7 9. Normative References . . . . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8
1. Requirements Language 1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2. Introduction 2. Introduction
Dual-Stack Lite [I-D.softwire-ds-lite] is a solution to offer both Dual-Stack Lite [I-D.softwire-ds-lite] is a solution to offer both
skipping to change at page 6, line 32 skipping to change at page 6, line 32
[I-D.softwire-ds-lite]. [I-D.softwire-ds-lite].
Note that a B4 system may have multiple network interfaces, and these Note that a B4 system may have multiple network interfaces, and these
interfaces may be configured differently; some may be connected to interfaces may be configured differently; some may be connected to
networks that call for DS-Lite, and some may be connected to networks networks that call for DS-Lite, and some may be connected to networks
that are using normal dual stack or other means. The B4 system that are using normal dual stack or other means. The B4 system
should approach this specification on an interface-by-interface should approach this specification on an interface-by-interface
basis. For example, if the B4 system is attached to multiple basis. For example, if the B4 system is attached to multiple
networks that provide the AFTR Name option, then the B4 system MUST networks that provide the AFTR Name option, then the B4 system MUST
configure a tunnel for each interface separately as each DS-Lite configure a tunnel for each interface separately as each DS-Lite
tunnel provides IPv4 connectivity for each distinct interface. tunnel provides IPv4 connectivity for each distinct interface. Means
to bind a AFTR Name and DS-Lite tunnel configuration to a given
interface in a multiple interfaces device are out of scope of this
document.
6. Security Considerations 6. Security Considerations
This document does not present any new security issues, but as with This document does not present any new security issues, but as with
all DHCPv6-derived configuration state, it is completely possible all DHCPv6-derived configuration state, it is completely possible
that the configuration is being delivered by a third party (Man In that the configuration is being delivered by a third party (Man In
The Middle). As such, there is no basis to trust that the access the The Middle). As such, there is no basis to trust that the access the
DS-Lite Softwire connection represents can be trusted, and it should DS-Lite Softwire connection represents can be trusted, and it should
not therefore bypass any security mechanisms such as IP firewalls. not therefore bypass any security mechanisms such as IP firewalls.
skipping to change at page 8, line 17 skipping to change at page 8, line 17
David W. Hankins David W. Hankins
Google, Inc. Google, Inc.
1600 Amphitheatre Parkway 1600 Amphitheatre Parkway
Mountain View, CA 94043 Mountain View, CA 94043
USA USA
Email: dhankins@google.com Email: dhankins@google.com
Tomasz Mrugalski Tomasz Mrugalski
Gdansk University of Technology Gdansk University of Technology
Storczykowa 22B/12 ul. Storczykowa 22B/12
Gdansk 80-177 Gdansk 80-177
Poland Poland
Phone: +48 698 088 272 Phone: +48 698 088 272
Email: tomasz.mrugalski@eti.pg.gda.pl Email: tomasz.mrugalski@eti.pg.gda.pl
 End of changes. 7 change blocks. 
8 lines changed or deleted 11 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/