draft-ietf-pim-join-attributes-02.txt   draft-ietf-pim-join-attributes-03.txt 
PIM WG A. Boers PIM WG A. Boers
Internet-Draft IJ. Wijnands Internet-Draft IJ. Wijnands
Intended status: Informational E. Rosen Intended status: Informational E. Rosen
Expires: April 26, 2007 Cisco Systems, Inc. Expires: November 21, 2007 Cisco Systems, Inc.
October 23, 2006 May 20, 2007
Format for using TLVs in PIM messages Format for using TLVs in PIM messages
draft-ietf-pim-join-attributes-02 draft-ietf-pim-join-attributes-03
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes 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. 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
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 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 April 26, 2007. This Internet-Draft will expire on November 21, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document describes a generic TLV attribute encoding format to be This document describes a generic TLV attribute encoding format to be
added to PIM join messages. added to PIM join messages.
Table of Contents Table of Contents
1. Conventions used in this document . . . . . . . . . . . . . . . 3 1. Conventions used in this document . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
skipping to change at page 2, line 21 skipping to change at page 2, line 21
3.2. Transitive attributes . . . . . . . . . . . . . . . . . . . 3 3.2. Transitive attributes . . . . . . . . . . . . . . . . . . . 3
3.3. Attribute Hello Option . . . . . . . . . . . . . . . . . . 3 3.3. Attribute Hello Option . . . . . . . . . . . . . . . . . . 3
3.4. Conflicting attributes . . . . . . . . . . . . . . . . . . 4 3.4. Conflicting attributes . . . . . . . . . . . . . . . . . . 4
3.5. Attribute Convergence . . . . . . . . . . . . . . . . . . . 5 3.5. Attribute Convergence . . . . . . . . . . . . . . . . . . . 5
3.6. Multiple attributes . . . . . . . . . . . . . . . . . . . . 5 3.6. Multiple attributes . . . . . . . . . . . . . . . . . . . . 5
3.7. Applicability of the attributes . . . . . . . . . . . . . . 5 3.7. Applicability of the attributes . . . . . . . . . . . . . . 5
3.8. PIM attribute packet format . . . . . . . . . . . . . . . . 5 3.8. PIM attribute packet format . . . . . . . . . . . . . . . . 5
3.8.1. PIM Join packet format . . . . . . . . . . . . . . . . 5 3.8.1. PIM Join packet format . . . . . . . . . . . . . . . . 5
3.8.2. PIM Attribute Hello option . . . . . . . . . . . . . . 6 3.8.2. PIM Attribute Hello option . . . . . . . . . . . . . . 6
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
7.1. Normative References . . . . . . . . . . . . . . . . . . . 7 7.1. Normative References . . . . . . . . . . . . . . . . . . . 7
7.2. Informative References . . . . . . . . . . . . . . . . . . 7 7.2. Informative References . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
Intellectual Property and Copyright Statements . . . . . . . . . . 9 Intellectual Property and Copyright Statements . . . . . . . . . . 9
1. Conventions used in this document 1. Conventions used in this document
In this document, the key words "MUST", "MUST NOT", "REQUIRED", In this document, the key words "MUST", "MUST NOT", "REQUIRED",
skipping to change at page 6, line 45 skipping to change at page 6, line 45
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OptionType = TBD | OptionLength = 0 | | OptionType = TBD | OptionLength = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option type: TBD. Option type: TBD.
4. IANA Considerations 4. IANA Considerations
This document requires a new PIM Hello Option value and a new PIM A new IANA registry is needed for PIM Join Attributes Types.
Join Encoding type. Additionally, a new PIM Hello value needs to be obtained from the PIM
Hello Option values 17 through 65000 assigned by the IANA.
5. Security Considerations 5. Security Considerations
Security of the join attribute is only guaranteed by the security of Security of the join attribute is only guaranteed by the security of
the PIM packet, so the security considerations for PIM join packets the PIM packet, so the security considerations for PIM join packets
as described in PIM-SM [RFC4601] apply here. as described in PIM-SM [RFC4601] apply here.
6. Acknowledgments 6. Acknowledgments
The authors would like to thank Stig Venaas, James Lingard, Bharat The authors would like to thank Stig Venaas, James Lingard, Bharat
skipping to change at page 9, line 7 skipping to change at page 9, line 7
Email: ice@cisco.com Email: ice@cisco.com
Eric Rosen Eric Rosen
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Avenue 1414 Massachusetts Avenue
Boxborough, Ma 01719 Boxborough, Ma 01719
Email: erosen@cisco.com Email: erosen@cisco.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights 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 might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
 End of changes. 8 change blocks. 
13 lines changed or deleted 14 lines changed or added

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