IP over Resilient Packet Rings (iporpr) Charter

IP over Resilient Packet Rings (iporpr)

This Working Group did not meet

NOTE: This charter is a snapshot of the 58th IETF Meeting in Minneapolis, Minnesota USA. It may now be out-of-date.

Last Modified: 2002-12-09

Chair(s):

Frank Kastenholz <fkastenholz@juniper.net>
Albert Herrera <a.herrera@rogers.com>

Internet Area Director(s):

Thomas Narten <narten@us.ibm.com>
Margaret Wasserman <margaret.wasserman@nokia.com>

Internet Area Advisor:

Thomas Narten <narten@us.ibm.com>

Technical Advisor(s):

Thomas Narten <narten@us.ibm.com>

Mailing Lists:

General Discussion: iporpr@ietf.org
To Subscribe: iporpr-request@ietf.org
In Body: subscribe iporpr
Archive: www.ietf.org/mail-archive/working-groups/iporpr/current/maillist.html

Description of Working Group:

Resilient Packet Rings, under development within the IEEE's 802.17 RPRWG, will provide substantial enhancements in both efficiency and flexibility over current bi-directional ring topologies. Benefits of resilient packet rings (RPRs) will include spatial re-use (full utilization of both counter-rotating rings) while maintaining APS-like protection switching during media faults. The 802.17 RPRWG may develop mechanisms for topology discovery, congestion control, and protection switching. Reference the IEEE 802.17 RPRWG at http://www.ieee802.org/17/ for further information.

IEEE 802.17 is currently work in progress with a planned final draft by the end of 2002.

The IPORPR Working Group within the IETF plans to develop the necessary standards for efficient interaction between L2 and L3. The IPORPR Framework draft (draft-ietf-iporpr-framework-##.txt) defines three levels of 802.17/IP interaction:

1. L3 view of an RPR ring as a traditional broadcast media.

2. L3 service interface to an RPR ring for specific resource/services requests.

3. Enhanced L3 awareness and interaction with an RPR ring.

Given the work-in-progress nature of 802.17, the IPORPR work group is chartered to develop the basic (core) set L3 functionality as it applies to 802.17. This is the first level of interaction as outlined on the framework document with a L3 view of the RPR ring as a traditional broadcast media similar to Ethernet.

The IPORPR working group will also continue to revise the framework internet-draft (draft-ietf-iporpr-framework-##.txt as of this writing). A final publication of this draft will be deferred until at least the Core Protocol specification is available. This will allow the framework to evolve, based on implementation experience.

FUTURE WORK:

Following the Core protocol set, a re-charter is required to develop an Extended protocol set which will be oriented towards the second and third level of 802.17/IP interaction. The intent is that the Extended protocol will build on the implementation experience of the first level. A re-chartering might also include MIB-related items for development in cooperation with IEEE 802.17. As another aspect of the rechartering, the working group may elect to defer publication of the framework until the Extended protocol is available.

The following enumerates possible issues and areas to be developed. The IPORPR working group should evaluate these as work progresses. These are some, but not all, of the issues that 'may' need to be addressed.

- Packet Encapsulation

- Address Mapping. This will probably be L3/L2 mapping, but the details will be clearer as 802.17 progresses.

- MTU issues such as default MTU selection

- Transport of Multicast and Broadcast packets

- Mapping of Diffserv to any QOS mechanisms developed for 802.17

- Network Management

- Routing Protocols

- MPLS

- Traffic Engineering

- Mapping of 802.17 customer separation mechanisms to MPLS/IP/L3 VPNs

Given the fluid nature of 802.17's work (in-progress), there is no degree of certainty as to which of these technical issues need to be addressed and which do not.

IPORPR INTERACTION WITH OTHER STANDARDS BODIES:

There are no formal liaisons between the IPORPR working group and other standards bodies.

The IPORPR working group shall not duplicate work being done in other working groups nor shall it do work that directly overlaps the responsibilities of other working groups. Where such issues arise, the working group chairs shall direct the participants to the other relevant working group and shall notify the other relevant working group's chairs of the issue.

The IPORPR WG will coordinate with relevant working groups within the IETF to leverage existing work. The WG may also generate requirements for other IETF WGs as needed. Additionally, the WG may collaborate with other standards bodies and interoperability forums engaged in IP over optical activities (e.g., including ITU-T) to share information, minimize duplication of effort, and coordinate activities in order to promote interoperability and serve the best interest of the industry.

IPORPR participants are STRONGLY ENCOURAGED to take part in any and all areas of 802.17, which are of interest to them. In particular, IEEE 802.17 is developing a MIB for the management of 802.17 networks. IPORPR participants are encouraged to take part in this effort to ensure that the MIB is appropriate for the Internet's operational needs.

Goals and Milestones:

Done		Publish first draft of the Core IP-over-RPR specification as an Internet Draft. This draft covers the first level of 802.17/IP interaction.
Feb 03		Publish second draft of the Core IP-over-RPR specification as an Internet Draft. This should be published in time for the March 2003 IETF meeting.
Feb 03		Publish revised IP-over-802.17 Framework document.
Mar 03		Re-evaluate and re-charter, with specific emphasis on plans for extended features as well as revisions or additions to the IP-over-802.17 Framework document.
Apr 03		Submit final draft to the Core protocol to the IESG for Proposed Standard Status.