draft-ietf-ccamp-gmpls-g-694-lambda-labels-02.txt   draft-ietf-ccamp-gmpls-g-694-lambda-labels-03.txt 
INTERNET DRAFT Tomohiro Otani INTERNET DRAFT Tomohiro Otani
Updates: RFC 3471 KDDI R&D Labs Updates: RFC 3471 KDDI
Intended status: standard track (Editor) Intended status: standard track (Editor)
Expires: Jan. 31, 2009 July 14, 2008 Expires: July 19, 2009 January 13, 2009
Generalized Labels for G.694 Lambda-Switching Capable Label Switching Generalized Labels for G.694 Lambda-Switching Capable Label Switching
Routers Routers
Document: draft-ietf-ccamp-gmpls-g-694-lambda-labels-02.txt Document: draft-ietf-ccamp-gmpls-g-694-lambda-labels-03.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with
applicable patent or other IPR claims of which he or she is aware the provisions of BCP 78 and BCP 79.
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-Drafts. other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six
and may be updated, replaced, or obsoleted by other documents at any months and may be updated, replaced, or obsoleted by other
time. It is inappropriate to use Internet-Drafts as reference documents at any time. It is inappropriate to use Internet-Drafts
material or to cite them other than as "work in progress." as reference material or to cite them other than as "work in
progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July 19, 2009.
Abstract Abstract
Technology in the optical domain is constantly evolving and as a Technology in the optical domain is constantly evolving and as a
consequence new equipment providing lambda switching capability has consequence new equipment providing lambda switching capability has
been developed and is currently being deployed. However, RFC 3471 has been developed and is currently being deployed. However, RFC 3471 has
defined that a wavelength label (section 3.2.1.1) "only has defined that a wavelength label (section 3.2.1.1) "only has
significance between two neighbors" and global wavelength continuity significance between two neighbors" and global wavelength continuity
is not considered. In order to achieve interoperability in a network is not considered. In order to achieve interoperability in a network
composed of next generation lambda switch-capable equipment, this composed of next generation lambda switch-capable equipment, this
document defines a standard lambda label format, being compliant with document defines a standard lambda label format, being compliant with
ITU-T G.694. Moreover some consideration on how to ensure lambda ITU-T G.694. Moreover some consideration on how to ensure lambda
continuity with RSVP-TE is provided. This document is a companion to continuity with RSVP-TE is provided. This document is a companion to
the Generalized Multi-Protocol Label Switching (GMPLS) signaling. It the Generalized Multi-Protocol Label Switching (GMPLS) signaling. It
defines the label format when Lambda Switching is requested in an all defines the label format when Lambda Switching is requested in an all
optical network. optical network.
Table of Contents Table of Contents
Status of this Memo................................................ 1
Abstract........................................................... 1 Abstract........................................................... 1
1. Introduction.................................................... 3 1. Introduction....................................................2
2. Conventions used in this document............................... 3 2. Conventions used in this document...............................2
3. Assumed network model and related problem statement............. 3 3. Assumed network model and related problem statement.............2
4. Label Related Formats........................................... 5 4. Label Related Formats........................................... 5
5. Security consideration.......................................... 8 5. Security Considerations.........................................8
6. Acknowledgement................................................. 8 6. IANA Considerations.............................................9
7. References...................................................... 8 7. Acknowledgement................................................10
7.1. Normative References.......................................... 8 8. References.....................................................11
7.2. Informative References........................................ 9 8.1. Normative References.........................................11
Editor's address................................................... 9 8.2. Informative References.......................................11
Contributors' address.............................................. 9 Appendix A. DWDM Example..........................................11
Intellectual property considerations.............................. 10 Appendix B. CWDM Example..........................................12
Copyright statement............................................... 10 Authors' address..................................................13
Intellectual property and Copyright Statement.....................14
1. Introduction 1. Introduction
As described in [RFC3945], Generalized MPLS (GMPLS) extends MPLS from As described in [RFC3945], Generalized MPLS (GMPLS) extends MPLS from
supporting only packet (Packet Switching Capable - PSC) interfaces supporting only packet (Packet Switching Capable - PSC) interfaces
and switching to also include support for four new classes of and switching to also include support for four new classes of
interfaces and switching: interfaces and switching:
o Layer-2 Switch Capable (L2SC) o Layer-2 Switch Capable (L2SC)
o Time-Division Multiplex (TDM) o Time-Division Multiplex (TDM)
o Lambda Switch Capable (LSC) o Lambda Switch Capable (LSC)
skipping to change at page 3, line 34 skipping to change at page 3, line 4
that is necessary to set up a wavelength-based LSP appropriately and that is necessary to set up a wavelength-based LSP appropriately and
the wavelength defined in [G.694] is widely utilized. the wavelength defined in [G.694] is widely utilized.
2. Conventions used in this document 2. Conventions used in this document
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].
3. Assumed network model and related problem statement 3. Assumed network model and related problem statement
Figure 1 depicts an all-optically switched network consisting of Figure 1 depicts an all-optically switched network consisting of
different vendor's optical network domains. Vendor A's network is a different vendor's optical network domains. Vendor A's network
ring topology that consists of ROADM or WXC, and vendor B's network consists of ROADM or WXC, and vendor B's network consists of PXCs and
is a mesh topology consisting of PXCs and DWDMs, otherwise both DWDMs, otherwise both vendors' networks might be based on the same
vendors' networks are based on the same technology. technology.
In this case, the use of standardized wavelength label information is In this case, the use of standardized wavelength label information is
quite significant to establish a wavelength-based LSP. It is also an quite significant to establish a wavelength-based LSP. It is also an
important constraint when conducting CSPF calculation for RSVP-TE important constraint when conducting CSPF calculation for RSVP-TE
signaling. The way the CSPF is performed is outside the scope of this signaling. The way the CSPF is performed is outside the scope of this
document, but defined in [GMPLS-CSPF]. document, but defined in [GMPLS-CSPF].
It is needless to say, a LSP must be appropriately provisioned It is needless to say, a LSP must be appropriately provisioned
between a selected pair of ports not only within Domain A but also between a selected pair of ports not only within Domain A but also
over multiple domains satisfying wavelength constraints. over multiple domains satisfying wavelength constraints.
skipping to change at page 4, line 43 skipping to change at page 4, line 11
+-------------------------------------------------------------+ +-------------------------------------------------------------+
| Domain A | Domain B | | Domain A | Domain B |
| | | | | |
| +---+ lambda 1 | +---+ | | +---+ lambda 1 | +---+ |
| | |---------------|---------| | | | | |---------------|---------| | |
| WDM | N | lambda 2 | | N | WDM | | WDM | N | lambda 2 | | N | WDM |
| =====| O |---------------|---------| O |===== | | =====| O |---------------|---------| O |===== |
| O | D | . | | D | O | | O | D | . | | D | O |
| T WDM | E | . | | E | WDM T | | T WDM | E | . | | E | WDM T |
| H =====| 2 | lambda n | | 7 |===== H | | H =====| 2 | lambda n | | 6 |===== H |
| E | |---------------|---------| | E | | E | |---------------|---------| | E |
| R +---+ | +---+ R | | R +---+ | +---+ R |
| | | | | |
| N +---+ | +---+ N | | N +---+ | +---+ N |
| O | | | | | O | | O | | | | | O |
| D WDM | N | | | N | WDM D | | D WDM | N | | | N | WDM D |
| E =====| O | WDM | | O |===== E | | E =====| O | WDM | | O |===== E |
| S | D |=========================| D | S | | S | D |=========================| D | S |
| WDM | E | | | E | WDM | | WDM | E | | | E | WDM |
| =====| 5 | | | 8 |===== | | =====| 5 | | | 8 |===== |
skipping to change at page 5, line 4 skipping to change at page 4, line 25
| N +---+ | +---+ N | | N +---+ | +---+ N |
| O | | | | | O | | O | | | | | O |
| D WDM | N | | | N | WDM D | | D WDM | N | | | N | WDM D |
| E =====| O | WDM | | O |===== E | | E =====| O | WDM | | O |===== E |
| S | D |=========================| D | S | | S | D |=========================| D | S |
| WDM | E | | | E | WDM | | WDM | E | | | E | WDM |
| =====| 5 | | | 8 |===== | | =====| 5 | | | 8 |===== |
| | | | | | | | | | | | | |
| +---+ | +---+ | | +---+ | +---+ |
+-------------------------------------------------------------+ +-------------------------------------------------------------+
Figure 2 Interconnecting details between two domains. Figure 2 Interconnecting details between two domains.
In the scenario of Figure 2, consider the setting up of a In the scenario of Figure 1, consider the setting up of a
bidirectional LSP from ingress switch 1 to egress switch 4. In order bidirectional LSP from ingress switch 1 to egress switch 9. In order
to satisfy wavelength continuity constraint, a fixed wavelength to satisfy wavelength continuity constraint, a fixed wavelength
(lambda 1) needs to be used in domain A and domain B. A Path message (lambda 1) needs to be used in domain A and domain B. A Path message
will be used for the signaling, the PATH message must contain the will be used for the signaling, the PATH message must contain the
upstream label and a label set object; both containing the same upstream label and a label set object; both containing the same
lambda. The label set object is made by only one sub channel that lambda. The label set object is made by only one sub channel that
must be same as the upstream label. The path setup will continue must be same as the upstream label. The path setup will continue
downstream to switch 4 by configuring each lambda switch based on the downstream to switch 9 by configuring each lambda switch based on the
wavelength label. This label allows the correct switching of lambda wavelength label. This label allows the correct switching of lambda
switches and the label contents needs to be used over the inter- switches and the label contents needs to be used over the inter-
domain. As same above, the path setup will continue downstream to domain. As same above, the path setup will continue downstream to
switch 7 by configuring lambda switch based on multiple wavelength switch 9 by configuring lambda switch based on multiple wavelength
labels. If the node has a tunable wavelength transponder, the tuning labels. If the node has a tunable wavelength transponder, the tuning
wavelength is considered as a part of wavelength switching operation. wavelength is considered as a part of wavelength switching operation.
Not using a standardized label would add undue burden on the operator Not using a standardized label would add undue burden on the operator
to enforce policy as each manufacturer may decide on a different to enforce policy as each manufacturer may decide on a different
representation and therefore each domain may have its own label representation and therefore each domain may have its own label
formats. Moreover, manual provisioning may lead to misconfiguration formats. Moreover, manual provisioning may lead to misconfiguration
if domain-specific labels are used. if domain-specific labels are used.
Therefore, a wavelength label should be standardized in order to Therefore, a wavelength label should be standardized in order to
skipping to change at page 6, line 24 skipping to change at page 5, line 46
, where n is an integer (positive, negative or 0) and channel spacing , where n is an integer (positive, negative or 0) and channel spacing
is defined to be 0.0125, 0.025, 0.05 or 0.1 THz. When wider channel is defined to be 0.0125, 0.025, 0.05 or 0.1 THz. When wider channel
spacing such as 0.2 THz is utilized, the combination of narrower spacing such as 0.2 THz is utilized, the combination of narrower
channel spacing and the value n can provide proper frequency with channel spacing and the value n can provide proper frequency with
that channel spacing. Channel spacing is not utilized to indicate the that channel spacing. Channel spacing is not utilized to indicate the
LSR capability but only to specify a frequency in signaling. LSR capability but only to specify a frequency in signaling.
For the other example of the case of the ITU-T CWDM grid, the spacing For the other example of the case of the ITU-T CWDM grid, the spacing
between different channels was defined to be 20nm, so we need to pass between different channels was defined to be 20nm, so we need to pass
the wavelength value in nm in this case. Examples of CWDM the wavelength value in nm in this case. Examples of CWDM
wavelengths are 1470, 1490, etc. nm. wavelengths are 1471, 1491, etc. nm.
The wavelength is calculated as follows The wavelength is calculated as follows
Wavelength (nm) = 1470 nm + n * 20 nm Wavelength (nm) = 1471 nm + n * 20 nm
The tables listed in [G.694.1] and [G.694.2] are not numbered and The tables listed in [G.694.1] and [G.694.2] are not numbered and
change with the changing frequency spacing as technology advances, so change with the changing frequency spacing as technology advances, so
an index is not appropriate in this case. an index is not appropriate in this case.
4.2 DWDM Wavelength Label 4.2 DWDM Wavelength Label
For the case of DWDM, the information carried in a Wavelength label For the case of DWDM, the information carried in a Wavelength label
is: is:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Grid | C.S | Reserved | n | |Grid | C.S | Reserved | n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
(1) Grid: 3 bits (1) Grid: 3 bits
skipping to change at page 7, line 14 skipping to change at page 6, line 35
|Future use| 3 - 7 | |Future use| 3 - 7 |
+----------+---------+ +----------+---------+
(2) C.S.(channel spacing): 4 bits (2) C.S.(channel spacing): 4 bits
DWDM channel spacing is defined as follows. DWDM channel spacing is defined as follows.
+----------+---------+ +----------+---------+
| C.S(GHz) | Value | | C.S(GHz) | Value |
+----------+---------+ +----------+---------+
| 12.5 | 1 | | 100 | 1 |
+----------+---------+ +----------+---------+
| 25 | 2 | | 50 | 2 |
+----------+---------+ +----------+---------+
| 50 | 3 | | 25 | 3 |
+----------+---------+ +----------+---------+
| 100 | 4 | | 12.5 | 4 |
+----------+---------+ +----------+---------+
|Future use| 5 - 15 | |Future use| 5 - 15 |
+----------+---------+ +----------+---------+
(3) n: 17 bits (3) n: 16 bits
n is an integer to take either a negative, zero or a positive value. n is an integer to take either a negative, zero or a positive value.
The value used to compute the frequency as shown above. The value used to compute the frequency as shown above.
4.3 CWDM Wavelength Label 4.3 CWDM Wavelength Label
For the case of CWDM, the information carried in a Wavelength label For the case of CWDM, the information carried in a Wavelength label
is: is:
0 1 2 3 0 1 2 3
skipping to change at page 8, line 16 skipping to change at page 7, line 39
CWDM channel spacing is defined as follows. CWDM channel spacing is defined as follows.
+----------+---------+ +----------+---------+
| C.S(nm) | Value | | C.S(nm) | Value |
+----------+---------+ +----------+---------+
| 20 | 1 | | 20 | 1 |
+----------+---------+ +----------+---------+
|Future use| 2 - 15 | |Future use| 2 - 15 |
+----------+---------+ +----------+---------+
(3) n: 17 bits (3) n: 16 bits
n is an integer. The value used to compute the wavelength as shown n is an integer. The value used to compute the wavelength as shown
above. above.
We do not need to define a new type as the information stored is We do not need to define a new type as the information stored is
either a port label or a wavelength label. Only the wavelength label either a port label or a wavelength label. Only the wavelength label
as above needs to be defined. as above needs to be defined.
5. Security consideration 5. Security Considerations
This document introduces no new security considerations to [RFC3473]. This document introduces no new security considerations to [RFC3473].
GMPLS security is described in section 11 of [RFC3471] and refers to GMPLS security is described in section 11 of [RFC3471] and refers to
[RFC3209] for RSVP-TE. [RFC3209] for RSVP-TE.
6. Acknowledgement 6. IANA Considerations
This document has no actions for IANA.
7. Acknowledgement
The authors would like to thank Adrian Farrel, Lawrence Mao, Zafar The authors would like to thank Adrian Farrel, Lawrence Mao, Zafar
Ali and Dan Li for the discussion. Ali, Dan Li and Daniele Ceccarelli for the discussion and their
comments.
7. References 8. References
7.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC
3209, December 2001. 3209, December 2001.
[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
(MPLS) Signaling Functional Description", RFC 3471, January 2003. (MPLS) Signaling Functional Description", RFC 3471, January 2003.
[RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching [RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching
(MPLS) Signaling - Resource ReserVation Protocol Traffic Engineering (MPLS) Signaling - Resource ReserVation Protocol Traffic Engineering
(RSVP-TE) Extensions", RFC 3473, January 2003. (RSVP-TE) Extensions", RFC 3473, January 2003.
[RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label Switching [RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label Switching
(GMPLS) Architecture", RFC 3945, October 2004. (GMPLS) Architecture", RFC 3945, October 2004.
7.2. Informative References 8.2. Informative References
[GMPLS-CSPF] Otani, T., et al, "Considering Generalized Multiprotocol [GMPLS-CSPF] Otani, T., et al, "Considering Generalized Multiprotocol
Label Switching Traffic Engineering Attributes During Path Label Switching Traffic Engineering Attributes During Path
Computation", draft-otani-ccamp-gmpls-cspf-constraints-07.txt, Nov. Computation", draft-otani-ccamp-gmpls-cspf-constraints-08.txt, Feb.
2007. 2008.
[G.694.1] ITU-T Recommendation G.694.1, "Spectral grids for WDM [G.694.1] ITU-T Recommendation G.694.1, "Spectral grids for WDM
applications: DWDM frequency grid", June 2002. applications: DWDM frequency grid", June 2002.
[G.694.2] ITU-T Recommendation G.694.2, "Spectral grids for WDM [G.694.2] ITU-T Recommendation G.694.2, "Spectral grids for WDM
applications: CWDM wavelength grid", December 2003. applications: CWDM wavelength grid", December 2003.
Editor's address Appendix A. DWDM Example
Tomohiro Otani Considering the network displayed in figure 1 it is possible to show
KDDI R&D Laboratories, Inc. an example of LSP set up using the lambda labels.
2-1-15 Ohara Kamifukuoka Saitama, 356-8502, Japan
Phone: +81-49-278-7357
Email: otani@kddilabs.jp
Contributors' address Node 1 receives the request for establishing an LSP from itself to
Node 9. The ITU-T grid to be used is the DWDM one, the channel
spacing is 50Ghz and the wavelength to be used is 193,35 THz.
Node 1 signals the LSP via a Path message including a Wavelength
Label structured as defined in section 4.2:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Grid | C.S | Reserved | n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where:
Grid = 1 : ITU-T DWDM grid
C.S. = 2 : 50 GHz channel spacing
n = 5 :
Frequency (THz) = 193.1 THz + n * channel spacing (THz)
193.35 (THz) = 193.1 (THz) + n* 0.05 (THz)
n = (193.35-193.1)/0.05 = 5
Appendix B. CWDM Example
The network displayed in figure 1 can be used also to display an
example of signaling using the Wavelength Label in a CWDM
environment.
This time the signaling of an LSP from Node 4 to Node 7 is
considered. Such LSP exploits the CWDM ITU-T grid with a 20nm
channel spacing and is to established using wavelength equal to 1331
nm.
Node 4 signals the LSP via a Path message including a Wavelength
Label structured as defined in section 4.3:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Grid | C.S | Reserved | n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where:
Grid = 2 : ITU-T CWDM grid
C.S. = 1 : 20 nm channel spacing
n = -7 :
Wavelength (nm) = 1471 nm + n * 20 nm
1331 (nm) = 1471 (nm) + n * 20 nm
n = (1331-1471)/20 = -7
Authors' address
Tomohiro Otani
KDDI Corporation
2-3-2 Nishishinjuku Shinjuku-ku Tokyo, 163-8003, Japan
Phone: +81-3-3347-6006
Email: tm-otani@kddi.com
Richard Rabbat Richard Rabbat
Google, Inc. Google, Inc.
1600 Amphitheatre Pkwy 1600 Amphitheatre Pkwy
Mountain View, CA 94043 Mountain View, CA 94043
Email: rabbat@alum.mit.edu Email: rabbat@alum.mit.edu
Sidney Shiba Sidney Shiba
Email: sidney.shiba@yahoo.com Email: sidney.shiba@yahoo.com
Hongxiang Guo Hongxiang Guo
KDDI R&D Laboratories, Inc. Email: hongxiang.guo@gmail.com
2-1-15 Ohara Fujimino Saitama, 356-8502, Japan.
Phone: +81-49-278-7864.
Email: ho-guo@kddilabs.jp
Keiji Miyazaki Keiji Miyazaki
Fujitsu Laboratories Ltd Fujitsu Laboratories Ltd
4-1-1 Kotanaka Nakahara-ku, Kawasaki Kanagawa, 211-8588, Japan 4-1-1 Kotanaka Nakahara-ku, Kawasaki Kanagawa, 211-8588, Japan
Phone: +81-44-754-2765 Phone: +81-44-754-2765
Email: miyazaki.keiji@jp.fujitsu.com Email: miyazaki.keiji@jp.fujitsu.com
Diego Caviglia Diego Caviglia
Ericsson Ericsson
16153 Genova Cornigliano, ITALY 16153 Genova Cornigliano, ITALY
Phone: +390106003736 Phone: +390106003736
Email: diego.caviglia@ericsson.com Email: diego.caviglia@ericsson.com
Intellectual property considerations Full Copyright Statement
The IETF takes no position regarding the validity or scope of any Copyright (c) 2009 IETF Trust and the persons identified as the
Intellectual Property Rights or other rights that might be claimed to document authors. All rights reserved.
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any This document is subject to BCP 78 and the IETF Trust's Legal
assurances of licenses to be made available, or the result of an Provisions Relating to IETF Documents
attempt made to obtain a general license or permission for the use of (http://trustee.ietf.org/license-info) in effect on the date of
such proprietary rights by implementers or users of this publication of this document. Please review these documents
specification can be obtained from the IETF on-line IPR repository at carefully, as they describe your rights and restrictions with respect
http://www.ietf.org/ipr. to this document.
All IETF Documents and the information contained therein are provided
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE
ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF Trust takes no position regarding the validity or scope of
any Intellectual Property Rights or other rights that might be
claimed to pertain to the implementation or use of the technology
described in any IETF Document or the extent to which any license
under such rights might or might not be available; nor does it
represent that it has made any independent effort to identify any
such rights.
Copies of Intellectual Property disclosures made to the IETF
Secretariat and any assurances of licenses to be made available, or
the result of an attempt made to obtain a general license or
permission for the use of such proprietary rights by implementers or
users of this specification can be obtained from the IETF on-line IPR
repository at http://www.ietf.org/ipr
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- any standard or specification contained in an IETF Document. Please
ipr@ietf.org. address the information to the IETF at ietf-ipr@ietf.org.
Copyright statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions The definitive version of an IETF Document is that published by, or
contained in BCP 78, and except as set forth therein, the authors under the auspices of, the IETF. Versions of IETF Documents that are
retain all their rights. published by third parties, including those that are translated into
other languages, should not be considered to be definitive versions
of IETF Documents. The definitive version of these Legal Provisions
is that published by, or under the auspices of, the IETF. Versions of
these Legal Provisions that are published by third parties, including
those that are translated into other languages, should not be
considered to be definitive versions of these Legal Provisions.
This document and the information contained herein are provided on an For the avoidance of doubt, each Contributor to the IETF Standards
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS Process licenses each Contribution that he or she makes as part of
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND the IETF Standards Process to the IETF Trust pursuant to the
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS provisions of RFC 5378. No language to the contrary, or terms,
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF conditions or rights that differ from or are inconsistent with the
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED rights and licenses granted under RFC 5378, shall have any effect and
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. shall be null and void, whether published or posted by such
Contributor, or included with or in such Contribution.
 End of changes. 44 change blocks. 
88 lines changed or deleted 174 lines changed or added

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