draft-ietf-rserpool-common-param-02.txt   draft-ietf-rserpool-common-param-03.txt 
Network Working Group R. Stewart Network Working Group R. Stewart
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Expires: April 1, 2003 Q. Xie Expires: August 27, 2003 Q. Xie
Motorola, Inc. Motorola, Inc.
M. Stillman M. Stillman
Nokia Nokia
M. Tuexen M. Tuexen
Siemens AG Siemens AG
October 1, 2002 February 26, 2003
Aggregate Server Access Protocol (ASAP) and Endpoint Name Resolution Aggregate Server Access Protocol (ASAP) and Endpoint Name Resolution
Protocol (ENRP) common parameters document Protocol (ENRP) common parameters document
draft-ietf-rserpool-common-param-02.txt draft-ietf-rserpool-common-param-03.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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- other groups may also distribute working documents as
Drafts. 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 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."
The list of current Internet-Drafts can be accessed at http:// The list of current Internet-Drafts can be accessed at http://
www.ietf.org/ietf/1id-abstracts.txt. 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 April 1, 2003. This Internet-Draft will expire on August 27, 2003.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
Aggregate Server Access Protocol (ASAP) [4] in conjunction with the Aggregate Server Access Protocol (ASAP) [4] in conjunction with the
Endpoint Name Resolution Protocol (ENRP) [5] provides a high Endpoint Name Resolution Protocol (ENRP) [5] provides a high
availability data transfer mechanism over IP networks. availability data transfer mechanism over IP networks.
Both protocols work together and so share many common parameters used Both protocols work together and so share many common parameters used
in message formats. This document details the common message in message formats. This document details the common message
parameters shared between the two protocols. This document provides parameters shared between the two protocols. This document provides
skipping to change at page 2, line 21 skipping to change at page 2, line 21
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Conventions . . . . . . . . . . . . . . . . . . . . . . . 3 1.1 Conventions . . . . . . . . . . . . . . . . . . . . . . . 3
2. Parameters in General . . . . . . . . . . . . . . . . . . 4 2. Parameters in General . . . . . . . . . . . . . . . . . . 4
3. ENRP-ASAP Common Parameters . . . . . . . . . . . . . . . 5 3. ENRP-ASAP Common Parameters . . . . . . . . . . . . . . . 5
3.1 IPv4 Address Parameter . . . . . . . . . . . . . . . . . . 6 3.1 IPv4 Address Parameter . . . . . . . . . . . . . . . . . . 6
3.2 IPv6 Address Parameter . . . . . . . . . . . . . . . . . . 7 3.2 IPv6 Address Parameter . . . . . . . . . . . . . . . . . . 7
3.3 SCTP Transport Parameter . . . . . . . . . . . . . . . . . 7 3.3 SCTP Transport Parameter . . . . . . . . . . . . . . . . . 7
3.4 TCP Transport Parameter . . . . . . . . . . . . . . . . . 8 3.4 TCP Transport Parameter . . . . . . . . . . . . . . . . . 8
3.5 UDP Transport Parameter . . . . . . . . . . . . . . . . . 9 3.5 UDP Transport Parameter . . . . . . . . . . . . . . . . . 9
3.6 Pool Member Selection Policy Parameter . . . . . . . . . . 10 3.6 Pool Member Selection Policy Parameter . . . . . . . . . . 10
3.6.1 Round Robin Policy . . . . . . . . . . . . . . . . . . . . 11 3.6.1 Round Robin Policy . . . . . . . . . . . . . . . . . . . . 12
3.6.2 Least Used Policy . . . . . . . . . . . . . . . . . . . . 11 3.6.2 Least Used Policy . . . . . . . . . . . . . . . . . . . . 12
3.6.3 Least Used with Degradation Policy . . . . . . . . . . . . 11 3.6.3 Least Used with Degradation Policy . . . . . . . . . . . . 12
3.6.4 Weighted Round Robin Policy . . . . . . . . . . . . . . . 12 3.6.4 Weighted Round Robin Policy . . . . . . . . . . . . . . . 13
3.7 Pool Handle Parameter . . . . . . . . . . . . . . . . . . 12 3.7 Pool Handle Parameter . . . . . . . . . . . . . . . . . . 13
3.8 Pool Element Parameter . . . . . . . . . . . . . . . . . . 12 3.8 Pool Element Parameter . . . . . . . . . . . . . . . . . . 13
3.9 Server Information Parameter . . . . . . . . . . . . . . . 14 3.9 Server Information Parameter . . . . . . . . . . . . . . . 15
3.10 Operation Error Parameter . . . . . . . . . . . . . . . . 15 3.10 Operation Error Parameter . . . . . . . . . . . . . . . . 16
3.10.1 Unrecognized Parameter Error . . . . . . . . . . . . . . . 16 3.10.1 Unrecognized Parameter Error . . . . . . . . . . . . . . . 17
3.10.2 Unrecognized Message Error . . . . . . . . . . . . . . . . 16 3.10.2 Unrecognized Message Error . . . . . . . . . . . . . . . . 17
3.11 Cookie Parameter . . . . . . . . . . . . . . . . . . . . . 16 3.11 Cookie Parameter . . . . . . . . . . . . . . . . . . . . . 17
3.12 PE Identifier Parameter . . . . . . . . . . . . . . . . . 17 3.12 PE Identifier Parameter . . . . . . . . . . . . . . . . . 18
4. Common Message Formats . . . . . . . . . . . . . . . . . . 18 3.13 Communication Restrictions Parameter . . . . . . . . . . . 18
5. Security Considerations . . . . . . . . . . . . . . . . . 20 4. Common Message Formats . . . . . . . . . . . . . . . . . . 20
Normative References . . . . . . . . . . . . . . . . . . . 21 5. Security Considerations . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . 21 Normative References . . . . . . . . . . . . . . . . . . . 23
Full Copyright Statement . . . . . . . . . . . . . . . . . 23 Authors' Addresses . . . . . . . . . . . . . . . . . . . . 23
Intellectual Property and Copyright Statements . . . . . . 25
1. Introduction 1. Introduction
Aggregate Server Access Protocol (ASAP) [4] in conjunction with the Aggregate Server Access Protocol (ASAP) [4] in conjunction with the
Endpoint Name Resolution Protocol (ENRP) [5] provides a high Endpoint Name Resolution Protocol (ENRP) [5] provides a high
availability data transfer mechanism over IP networks. availability data transfer mechanism over IP networks.
Both protocols work together and so share many common parameters used Both protocols work together and so share many common parameters used
in message formats. This document details the common message in message formats. This document details the common message
parameters shared between the two protocols. This document provides parameters shared between the two protocols. This document provides
skipping to change at page 6, line 41 skipping to change at page 6, line 41
0x3 - SCTP Transport 0x3 - SCTP Transport
0x4 - TCP Transport 0x4 - TCP Transport
0x5 - UDP Transport 0x5 - UDP Transport
0x6 - Pool Member Selection Policy 0x6 - Pool Member Selection Policy
0x7 - Pool Handle 0x7 - Pool Handle
0x8 - Pool Element 0x8 - Pool Element
0x9 - Server Information 0x9 - Server Information
0xa - Operation Error 0xa - Operation Error
0xb - Cookie 0xb - Cookie
0xc - PE Identifier 0xc - PE Identifier
0xd - Communication restrictions
others - (reserved by IETF) others - (reserved by IETF)
3.1 IPv4 Address Parameter 3.1 IPv4 Address Parameter
This parameter defines a TLV that carries an IPv4 address. This parameter defines a TLV that carries an IPv4 address.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 8, line 10 skipping to change at page 8, line 10
3.3 SCTP Transport Parameter 3.3 SCTP Transport Parameter
This parameter defines a TLV that describes a user transport using This parameter defines a TLV that describes a user transport using
SCTP protocol. SCTP protocol.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x3 | Length = variable | | Type = 0x3 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCTP port | (reserved) | | SCTP port | Transport Use |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 or IPv6 Address #1 : : IPv4 or IPv6 Address #1 :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: : : :
: ... : : ... :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 or IPv6 Address #n : : IPv4 or IPv6 Address #n :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Length: 16 bits (unsigned integer)
Indicates the entire length of the parameter in number of octets, Indicates the entire length of the parameter in number of octets,
including the Type, Length, SCTP port, reserved fields, and all IP including the Type, Length, SCTP port, reserved fields, and all IP
address parameters present. address parameters present.
SCTP port: 16 bits (unsigned integer) SCTP port: 16 bits (unsigned integer)
The SCTP port number signed to this SCTP user transport. The SCTP port number signed to this SCTP user transport.
Transport use: 16 bits (unsigned interger)
This field represents how the pool element intends this transport
address to be used. The field MUST be populated with one of the
following values:
Type | Value
------------------+----------------
CONTROL or DATA | 0x0000
CONTROL ONLY | 0x0001
DATA ONLY | 0x0002
IPv4 or IPv6 Address #1 - #n: IPv4 or IPv6 Address #1 - #n:
Each indicates an IPv4 or IPv6 address parameter (as defined above in Each indicates an IPv4 or IPv6 address parameter (as defined above in
Section 3.1 and Section 3.2) assigned to this SCTP user transport. Section 3.1 and Section 3.2) assigned to this SCTP user transport.
At least one IP address parameter MUST be present in an SCTP At least one IP address parameter MUST be present in an SCTP
transport parameter. transport parameter.
3.4 TCP Transport Parameter 3.4 TCP Transport Parameter
This parameter defines a TLV that describes a user transport using This parameter defines a TLV that describes a user transport using
TCP protocol. TCP protocol.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x4 | Length = variable | | Type = 0x4 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TCP port | (reserved) | | TCP port | Transport Use |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 or IPv6 Address : : IPv4 or IPv6 Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Length: 16 bits (unsigned integer)
Indicates the entire length of the parameter in number of octets, Indicates the entire length of the parameter in number of octets,
including the Type, Length, TCP port, reserved fields, and IP address including the Type, Length, TCP port, reserved fields, and IP address
parameter. parameter.
TCP port: 16 bits (unsigned integer) TCP port: 16 bits (unsigned integer)
The TCP port number signed to this TCP user transport. The TCP port number signed to this TCP user transport.
Transport use: 16 bits (unsigned interger)
This field represents how the pool element intends this transport
address to be used. The field MUST be populated with one of the
following values:
Type | Value
------------------+----------------
CONTROL or DATA | 0x0000
CONTROL ONLY | 0x0001
DATA ONLY | 0x0002
IPv4 or IPv6 Address: IPv4 or IPv6 Address:
Indicates an IPv4 or IPv6 address parameter (as defined above in Indicates an IPv4 or IPv6 address parameter (as defined above in
Section 3.1 and Section 3.2) assigned to this TCP user transport. Section 3.1 and Section 3.2) assigned to this TCP user transport.
Unlike in an SCTP transport, only one IP address parameter can be Unlike in an SCTP transport, only one IP address parameter can be
present in a TCP transport parameter. present in a TCP transport parameter.
3.5 UDP Transport Parameter 3.5 UDP Transport Parameter
This parameter defines a TLV that describes a user transport using This parameter defines a TLV that describes a user transport using
skipping to change at page 10, line 5 skipping to change at page 10, line 32
The UDP port number signed to this UDP user transport. The UDP port number signed to this UDP user transport.
IPv4 or IPv6 Address: IPv4 or IPv6 Address:
Indicates an IPv4 or IPv6 address parameter (as defined above in Indicates an IPv4 or IPv6 address parameter (as defined above in
Section 3.1 and Section 3.2) assigned to this UDP user transport. Section 3.1 and Section 3.2) assigned to this UDP user transport.
Unlike in an SCTP transport, only one IP address parameter can be Unlike in an SCTP transport, only one IP address parameter can be
present in a UDP transport parameter. present in a UDP transport parameter.
Note: A UDP port MUST NOT be used for control information. For this
reason, no Transport Use field is provided. UDP MUST always be
treated as a "Data Only" type transport use.
3.6 Pool Member Selection Policy Parameter 3.6 Pool Member Selection Policy Parameter
This parameter defines a pool member selection policy. RSERPOOL This parameter defines a pool member selection policy. RSERPOOL
supports multiple pool member selection polices and also allows supports multiple pool member selection polices and also allows
definition of new selection polices in the future. definition of new selection polices in the future.
The enforcement rules and handling procedures of all the policies are The enforcement rules and handling procedures of all the policies are
defined in Section xxxxx in ASAP [4]. defined in Section xxxxx in ASAP [4].
All pool member selection policies, both present and future, MUST use All pool member selection policies, both present and future, MUST use
skipping to change at page 10, line 28 skipping to change at page 11, line 16
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x6 | Length = variable | | Type = 0x6 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy Type | Policy-specific Data.... | Policy Type | Policy-specific Data....
+-+-+-+-+-+-+-+-+------------------------------------------------ +-+-+-+-+-+-+-+-+------------------------------------------------
Length: 16 bits (unsigned integer) Length: 16 bits (unsigned integer)
Indicates the entire length of the parameter in number of octets, Indicates the entire length of the parameter in number of octets,
including the Type, Length, Policy Type fields, and the Policy- including the Type, Length, Policy Type fields, and the
specific Data. Policy-specific Data.
Note, the value in Length field will NOT cover any padding at the end Note, the value in Length field will NOT cover any padding at the end
of the parameter, if there is one. of the parameter, if there is one.
Policy Type: 8 bits (unsigned integer) Policy Type: 8 bits (unsigned integer)
Specifies the type of selection policy. Specifies the type of selection policy.
Currently defined policy types are: Currently defined policy types are:
skipping to change at page 18, line 5 skipping to change at page 18, line 31
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PE Identifier | | PE Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PE Identifier: 32 bits (unsigned integer) PE Identifier: 32 bits (unsigned integer)
Uniquely identifies the PE in the pool. The PE picks its identifier Uniquely identifies the PE in the pool. The PE picks its identifier
when it starts up. See Section ???? in [ASAP] for recommendations on when it starts up. See Section ???? in [ASAP] for recommendations on
PE identifier generation. PE identifier generation.
3.13 Communication Restrictions Parameter
This parameter defines a TLV that can be used by the sender to
restrict name server searches to a limited number of transport types.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0xd | Length=0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Control Type | Data Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Control Type: 16 bits (unsigned integer)
This field requests the search be restricted to PE's that have a
control channel type of the specified value. One of the following
values MUST be used:
Type | Value
-----------+-------------
ANY | 0x0000
SCTP ONLY | 0x0001
TCP ONLY | 0x0002
Data Type: 16 bits (unsigned integer)
This field requests the search be restricted to PE's that have a data
channel type of the specified type. One of the following values MUST
be used:
Type | Value
-----------+-------------
ANY | 0x0000
SCTP ONLY | 0x0001
TCP ONLY | 0x0002
UDP ONLY | 0x0003
4. Common Message Formats 4. Common Message Formats
The figure below illustrates the common format for all ASAP and ENRP The figure below illustrates the common format for all ASAP and ENRP
messages. Each message is formatted with a Message Type field, a messages. Each message is formatted with a Message Type field, a
message-specific Flag field, a Message Length field, and a Value message-specific Flag field, a Message Length field, and a Value
field. field.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 22, line 15 skipping to change at page 24, line 15
Nokia Nokia
127 W. State Street 127 W. State Street
Ithaca, NY 14850 Ithaca, NY 14850
USA USA
Phone: +1-607-273-0724 Phone: +1-607-273-0724
EMail: maureen.stillman@nokia.com EMail: maureen.stillman@nokia.com
Michael Tuexen Michael Tuexen
Siemens AG Siemens AG
ICN WN CC SE 7
D-81359 Munich
Germany Germany
Phone: +49 89 722 47210 Phone:
EMail: Michael.Tuexen@siemens.com EMail: tuexen@fh-muenster.de
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
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; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication 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 implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement Acknowledgement
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/