draft-ietf-mboned-auto-multicast-08.txt   draft-ietf-mboned-auto-multicast-09.txt 
Network Working Group D. Thaler Network Working Group D. Thaler
Internet-Draft M. Talwar Internet-Draft M. Talwar
Intended status: Standards Track A. Aggarwal Intended status: Standards Track A. Aggarwal
Expires: April 5, 2008 Microsoft Corporation Expires: December 29, 2008 Microsoft Corporation
L. Vicisano L. Vicisano
Cisco Systems Cisco Systems
T. Pusateri T. Pusateri
!j !j
October 3, 2007 June 27, 2008
Automatic IP Multicast Without Explicit Tunnels (AMT) Automatic IP Multicast Without Explicit Tunnels (AMT)
draft-ietf-mboned-auto-multicast-08 draft-ietf-mboned-auto-multicast-09
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 39 skipping to change at page 1, line 39
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 5, 2008. This Internet-Draft will expire on December 29, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract Abstract
Automatic Multicast Tunneling (AMT) allows multicast communication Automatic Multicast Tunneling (AMT) allows multicast communication
amongst isolated multicast-enabled sites or hosts, attached to a amongst isolated multicast-enabled sites or hosts, attached to a
network which has no native multicast support. It also enables them network which has no native multicast support. It also enables them
to exchange multicast traffic with the native multicast to exchange multicast traffic with the native multicast
infrastructure and does not require any manual configuration. AMT infrastructure and does not require any manual configuration. AMT
uses an encapsulation interface so that no changes to a host stack or uses an encapsulation interface so that no changes to a host stack or
applications are required, all protocols (not just UDP) are handled, applications are required, all protocols (not just UDP) are handled,
skipping to change at page 30, line 32 skipping to change at page 30, line 32
previously set aside the range 2001::/16 for allocating prefixes for previously set aside the range 2001::/16 for allocating prefixes for
this purpose. this purpose.
9.2. IPv4 and IPv6 AMT Subnet Prefix Allocation 9.2. IPv4 and IPv6 AMT Subnet Prefix Allocation
It should also be noted that this prefix length directly affects the It should also be noted that this prefix length directly affects the
number of groups available to be created by the AMT gateway: in the number of groups available to be created by the AMT gateway: in the
IPv4 case, a prefix length of 16 gives 256 groups, and a prefix IPv4 case, a prefix length of 16 gives 256 groups, and a prefix
length of 8 gives 65536 groups. length of 8 gives 65536 groups.
All allocations are a one time effort and there will be no need for
any recurring assignment after this stage.
9.2.1. IPv4 9.2.1. IPv4
As described above in Section 7.2.1 an IPv4 prefix with a length of As described above in Section 7.2.1 an IPv4 prefix with a length of
16 is requested for this purpose. 16 is requested for this purpose.
9.2.2. IPv6 9.2.2. IPv6
As described above in Section 7.2.2 an IPv6 prefix with a length of As described above in Section 7.2.2 an IPv6 prefix with a length of
32 is requested. 32 is requested.
9.3. UDP Port number 9.3. UDP Port number
IANA has previously allocated UDP reserved port number 2268 for AMT IANA has previously allocated UDP reserved port number 2268 for AMT
encapsulation. encapsulation.
All allocations are a one time effort and there will be no need for
any recurring assignment after this stage.
10. Security Considerations 10. Security Considerations
The anycast technique introduces a risk that a rogue router or a The anycast technique introduces a risk that a rogue router or a
rogue AS could introduce a bogus route to the AMT Relay Anycast rogue AS could introduce a bogus route to the AMT Relay Anycast
prefix, and thus divert the traffic. Network managers have to prefix, and thus divert the traffic. Network managers have to
guarantee the integrity of their routing to the AMT Relay Anycast guarantee the integrity of their routing to the AMT Relay Anycast
prefix in much the same way that they guarantee the integrity of all prefix in much the same way that they guarantee the integrity of all
other routes. other routes.
Within the native MBGP infrastructure, there is a risk that a rogue Within the native MBGP infrastructure, there is a risk that a rogue
skipping to change at page 38, line 7 skipping to change at page 38, line 7
Tom Pusateri Tom Pusateri
!j !j
222 E. Jones Ave. 222 E. Jones Ave.
Wake Forest, NC 27587 Wake Forest, NC 27587
USA USA
Email: pusateri@bangj.com Email: pusateri@bangj.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). 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
skipping to change at page 38, line 44 skipping to change at line 1397
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
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 this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 8 change blocks. 
12 lines changed or deleted 8 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/