draft-ietf-v6ops-ula-usage-recommendations-04.txt   draft-ietf-v6ops-ula-usage-recommendations-05.txt 
Internet Engineering Task Force B. Liu Internet Engineering Task Force B. Liu
Internet-Draft S. Jiang Internet-Draft S. Jiang
Intended status: Informational Huawei Technologies Intended status: Informational Huawei Technologies
Expires: April 30, 2015 October 27, 2014 Expires: November 3, 2015 May 2, 2015
Considerations For Using Unique Local Addresses Considerations For Using Unique Local Addresses
draft-ietf-v6ops-ula-usage-recommendations-04 draft-ietf-v6ops-ula-usage-recommendations-05
Abstract Abstract
This document provides considerations for using IPv6 Unique Local This document provides considerations for using IPv6 Unique Local
Addresses (ULAs). It identifies cases where ULA addresses are Addresses (ULAs). It identifies cases where ULA addresses are
helpful as well as potential problems that their use could introduce, helpful as well as potential problems that their use could introduce,
based on an analysis of different ULA usage scenarios. based on an analysis of different ULA usage scenarios.
Status of This Memo Status of This Memo
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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 April 30, 2015. This Internet-Draft will expire on November 3, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 14, line 21 skipping to change at page 14, line 21
10.2. Informative References 10.2. Informative References
[I-D.baker-v6ops-b2b-private-routing] [I-D.baker-v6ops-b2b-private-routing]
Baker, F., "Business to Business Private Routing", draft- Baker, F., "Business to Business Private Routing", draft-
baker-v6ops-b2b-private-routing-00 (work in progress), baker-v6ops-b2b-private-routing-00 (work in progress),
July 2007. July 2007.
[I-D.ietf-v6ops-dhcpv6-slaac-problem] [I-D.ietf-v6ops-dhcpv6-slaac-problem]
Liu, B., Jiang, S., Bonica, R., Gong, X., and W. Wang, Liu, B., Jiang, S., Bonica, R., Gong, X., and W. Wang,
"DHCPv6/SLAAC Address Configuration Interaction Problem "DHCPv6/SLAAC Address Configuration Interaction Problem
Statement", draft-ietf-v6ops-dhcpv6-slaac-problem-02 (work Statement", draft-ietf-v6ops-dhcpv6-slaac-problem-03 (work
in progress), October 2014. in progress), October 2014.
[I-D.jhlee-mext-mnpp] [I-D.jhlee-mext-mnpp]
Tsukada, M., Ernst, T., and J. Lee, "Mobile Network Prefix Tsukada, M., Ernst, T., and J. Lee, "Mobile Network Prefix
Provisioning", draft-jhlee-mext-mnpp-00 (work in Provisioning", draft-jhlee-mext-mnpp-00 (work in
progress), October 2009. progress), October 2009.
[I-D.petrescu-autoconf-ra-based-routing] [I-D.petrescu-autoconf-ra-based-routing]
Petrescu, A., Janneteau, C., Demailly, N., and S. Imadali, Petrescu, A., Janneteau, C., Demailly, N., and S. Imadali,
"Router Advertisements for Routing between Moving "Router Advertisements for Routing between Moving
Networks", draft-petrescu-autoconf-ra-based-routing-05 Networks", draft-petrescu-autoconf-ra-based-routing-05
(work in progress), July 2014. (work in progress), July 2014.
[MIL-STD-1397] [MIL-STD-1397]
"Military Standard, Input/Output Interfaces, Standard "Military Standard, Input/Output Interfaces, Standard
Digital Data, Navy Systems (MIL-STD-1397B), 3 March 1989", Digital Data, Navy Systems (MIL-STD-1397B), 3 March 1989".
.
[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and [RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and
E. Lear, "Address Allocation for Private Internets", BCP E. Lear, "Address Allocation for Private Internets", BCP
5, RFC 1918, February 1996. 5, RFC 1918, February 1996.
[RFC2993] Hain, T., "Architectural Implications of NAT", RFC 2993, [RFC2993] Hain, T., "Architectural Implications of NAT", RFC 2993,
November 2000. November 2000.
[RFC3027] Holdrege, M. and P. Srisuresh, "Protocol Complications [RFC3027] Holdrege, M. and P. Srisuresh, "Protocol Complications
with the IP Network Address Translator", RFC 3027, January with the IP Network Address Translator", RFC 3027, January
skipping to change at page 16, line 10 skipping to change at page 16, line 10
[RFC7084] Singh, H., Beebee, W., Donley, C., and B. Stark, "Basic [RFC7084] Singh, H., Beebee, W., Donley, C., and B. Stark, "Basic
Requirements for IPv6 Customer Edge Routers", RFC 7084, Requirements for IPv6 Customer Edge Routers", RFC 7084,
November 2013. November 2013.
[RFC7269] Chen, G., Cao, Z., Xie, C., and D. Binet, "NAT64 [RFC7269] Chen, G., Cao, Z., Xie, C., and D. Binet, "NAT64
Deployment Options and Experience", RFC 7269, June 2014. Deployment Options and Experience", RFC 7269, June 2014.
[RS-485] "Electronic Industries Association (1983). Electrical [RS-485] "Electronic Industries Association (1983). Electrical
Characteristics of Generators and Receivers for Use in Characteristics of Generators and Receivers for Use in
Balanced Multipoint Systems. EIA Standard RS-485.", . Balanced Multipoint Systems. EIA Standard RS-485.".
[SCADA] "Boyer, Stuart A. (2010). SCADA Supervisory Control and [SCADA] "Boyer, Stuart A. (2010). SCADA Supervisory Control and
Data Acquisition. USA: ISA - International Society of Data Acquisition. USA: ISA - International Society of
Automation.", . Automation.".
[ULA-IN-WILD] [ULA-IN-WILD]
"G. Michaelson, "conference.apnic.net/data/36/apnic- "G. Michaelson, "conference.apnic.net/data/36/apnic-
36-ula_1377495768.pdf"", . 36-ula_1377495768.pdf"".
Authors' Addresses Authors' Addresses
Bing Liu Bing Liu
Huawei Technologies Huawei Technologies
Q14, Huawei Campus, No.156 Beiqing Road Q14, Huawei Campus, No.156 Beiqing Road
Hai-Dian District, Beijing, 100095 Hai-Dian District, Beijing, 100095
P.R. China P.R. China
Email: leo.liubing@huawei.com Email: leo.liubing@huawei.com
 End of changes. 9 change blocks. 
10 lines changed or deleted 9 lines changed or added

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