draft-ietf-softwire-bgp-te-attribute-00.txt   draft-ietf-softwire-bgp-te-attribute-01.txt 
Network Working Group Hamid Ould-Brahim (Nortel Networks) Network Working Group Hamid Ould-Brahim (Nortel Networks)
Internet Draft Don Fedyk (Nortel Networks) Internet Draft Don Fedyk (Nortel Networks)
Expiration Date: July 2008 Yakov Rekhter (Juniper Networks) Expiration Date: February 2009 Yakov Rekhter (Juniper Networks)
Intended Status: Proposed Standard Intended Status: Proposed Standard
Traffic Engineering Attribute Traffic Engineering Attribute
draft-ietf-softwire-bgp-te-attribute-00.txt draft-ietf-softwire-bgp-te-attribute-01.txt
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 4, line 20 skipping to change at page 4, line 20
The Minimum LSP Bandwidth is encoded in a 4 octet field in the IEEE The Minimum LSP Bandwidth is encoded in a 4 octet field in the IEEE
floating point format. The units are bytes (not bits!) per second. floating point format. The units are bytes (not bits!) per second.
The indication of whether the interface supports Standard or The indication of whether the interface supports Standard or
Arbitrary SONET/SDH is encoded as 1 octet. The value of this octet Arbitrary SONET/SDH is encoded as 1 octet. The value of this octet
is 0 if the interface supports Standard SONET/SDH, and 1 if the is 0 if the interface supports Standard SONET/SDH, and 1 if the
interface supports Arbitrary SONET/SDH. interface supports Arbitrary SONET/SDH.
When the Switching Capability field is LSC, there is no Switching When the Switching Capability field is LSC, there is no Switching
Capability specific information field present. Capability specific information field present.
4. IANA Considerations 4. Implication on aggregation
Routes that carry the Traffic Engineering Attribute have additional
semantics that could affect traffic forwarding behavior. Therefore,
such routes SHALL NOT be aggregated unless they share identical
Traffic Engineering Attributes.
5. IANA Considerations
This document defines a new BGP attribute. This attribute is optional This document defines a new BGP attribute. This attribute is optional
and non-transitive. and non-transitive.
5. Security Considerations 6. Security Considerations
This extension to BGP does not change the underlying security issues This extension to BGP does not change the underlying security issues
inherent in the existing BGP. inherent in the existing BGP.
6. Intellectual Property Statement 7. Intellectual Property Statement
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
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 5, line 9 skipping to change at page 5, line 29
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. 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- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
7. Copyright (C) The IETF Trust (2008). 8. Copyright (C) The IETF Trust (2008).
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, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE 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.
8. Acknowledgements 9. Acknowledgements
The authors would like to thank John Scudder for his review and The authors would like to thank John Scudder and Jeffrey Haas for
comments. their review and comments.
9. Normative References 10. Normative References
[BGP-4] Rekhter, Y., T. Li, Hares, S., "A Border Gateway Protocol 4 [BGP-4] Rekhter, Y., T. Li, Hares, S., "A Border Gateway Protocol 4
(BGP-4)", RFC4271, January 2006. (BGP-4)", RFC4271, January 2006.
[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.
[GMPLS-SIG] Berger, L., "Generalized Multi-Protocol Label Switching [GMPLS-SIG] Berger, L., "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Functional Description", RFC 3471, January 2003. (GMPLS) Signaling Functional Description", RFC 3471, January 2003.
[IEEE] IEEE, "IEEE Standard for Binary Floating-Point Arithmetic", [IEEE] IEEE, "IEEE Standard for Binary Floating-Point Arithmetic",
Standard 754-1985, 1985 (ISBN 1-5593-7653-8). Standard 754-1985, 1985 (ISBN 1-5593-7653-8).
10. Non-Normative References 11. Non-Normative References
[RFC4203] Kompella, K., Rekhter, Y., "OSPF Extensions in Support of [RFC4203] Kompella, K., Rekhter, Y., "OSPF Extensions in Support of
Generalized Multi-Protocol Label Switching (GMPLS)", RFC4203, October Generalized Multi-Protocol Label Switching (GMPLS)", RFC4203, October
2005 2005
[RFC4205] Kompella, K., Rekhter, Y., "Intermediate System to [RFC4205] Kompella, K., Rekhter, Y., "Intermediate System to
Intermediate System (IS-IS) Extensions in Support of Generalized Intermediate System (IS-IS) Extensions in Support of Generalized
Multi-Protocol Label Switching (GMPLS)", RFC4205, October 2005 Multi-Protocol Label Switching (GMPLS)", RFC4205, October 2005
[L1VPN] Fedyk, D., Ould-Brahim, H., Rekhter, Y., "BGP-based Auto- [L1VPN] Fedyk, D., Ould-Brahim, H., Rekhter, Y., "BGP-based Auto-
Discovery for L1VPNs", draft-ietf-l1vpn-bgp-auto-discovery, work in Discovery for L1VPNs", draft-ietf-l1vpn-bgp-auto-discovery, work in
progress progress
11. Author Information 12. Author Information
Hamid Ould-Brahim Hamid Ould-Brahim
Nortel Networks Nortel Networks
Email: hbrahim@nortel.com Email: hbrahim@nortel.com
Don Fedyk Don Fedyk
Nortel Networks Nortel Networks
Email: dwfedyk@nortel.com Email: dwfedyk@nortel.com
Yakov Rekhter Yakov Rekhter
 End of changes. 11 change blocks. 
12 lines changed or deleted 19 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/