Internetworking Over NBMA (ion)
This Working Group Did Not Meet
NOTE: This charter is a snapshot of the 45th IETF Meeting in Oslo, Norway. It may now be out-of-date. Last Modified: 17-May-99
Chair(s):
Andy Malis <malis@ascend.com>
Internet Area Director(s):
Thomas Narten <narten@raleigh.ibm.com>
Erik Nordmark <nordmark@eng.sun.com>
Internet Area Advisor:
Erik Nordmark <nordmark@eng.sun.com>
Mailing Lists:
General Discussion:ion@sunroof.eng.sun.com
To Subscribe: majordomo@sunroof.eng.sun.com
In Body: In Body: subscribe ion
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ion
Description of Working Group:
Note: This Working Group is jointly chartered by the Routing Area. The Routing Area Director: Joel Halpern (jhalpern@newbridge.com)
Motivation
The Internetworking Over NBMA Working Group was formed to combine the work of two previous working groups, IP Over ATM (ipatm) and Routing Over Large Clouds (rolc), because these two groups were often working very closely together on similar, if not identical, problems and solutions. The group will be evolutionary, not revolutionary; it will continue the work in the previous groups on the NBMA Next Hop Resolution Protocol (NHRP), IPv4 over ATM, and IPv6 over ATM.
Description
This WG will focus on the issues involved in internetworking network layer protocols over NBMA (non-broadcast multiple access) subnetwork technologies, such as ATM, Frame Relay, SMDS, and X.25 private and public networks. The group will endeavor to make all its solutions applicable to the entire range of network layer protocols and NBMA subnetworks. We recognize, however, that there will be cases where specific optimizations to IPv4, IPv6, and particular subnetwork technologies will result in better service to the user.
The group will focus on protocols for encapsulation, multicasting, addressing, address resolution and neighbor discovery, interactions with and optimization of internetworking-layer routing protocols when run over NBMA subnetworks, and protocol-specific network management support, as appropriate. The working group will submit these protocols for standardization.
The working group may also produce experimental and informational documents, including "Best Current Practices" guidelines, as required.
For ATM, the WG will continue the ipatm WG's transition from the LIS model described in RFC 1577 to the generalized NHRP model developed by the rolc WG, including a transition plan for existing networks.
The working group will coordinate its activities with the following other working groups:
1) Integrated Services over Specific Lower Layers (issll), for coordinating Quality of Service (QoS) issues and the implementation of IP integrated services capabilities (RSVP, the service models, etc.) over NBMA networks.
2) IP Next Generation (ipng), for IPv6 over ATM coordination.
The working group will also coordinate its work with other relevant standards bodies (e.g., ATM Forum, Frame Relay Forum, ANSI T1S1, ITU-T) and make recommendations to these organizations regarding the requirements for IP internetworking where the current published subnetwork standards, practices, or functionality do not meet the needs of internetworking.
The working group will not develop subnetwork layer standards.
Goals and Milestones:
Done |
|
Begin work on internetworking over Frame Relay SVCs (RFC 1490 extension), using NHRP for address resolution. |
Done |
|
Revise drafts on NHRP, 1577 revisions, server synchronization (applicable to both NHRP and ATMARP), multicast server and broadcast for ATM, IPv6 neighbor discovery, ATM UNI 4.0 signaling (RFC 1755 update), Classical IP and NHRP MIBs, NHRP applicability, ATMARP to NHRP transition plan, and router-router NHRP. |
Done |
|
IAB and IESG review of WG Status, and plans. This meeting will be scheduled to occur during SIGCOMM '96. |
Done |
|
Submit NHRP, RFC 1577 revisions, and server synchronization to the IESG as a Proposed Standard, complete the ATMARP to NHRP transition plan and NHRP applicability statement, revise drafts on multicast server and broadcast for ATM, IPv6 neighbor discovery, classical IP and NHRP MIBs, router-router NHRP, ATM UNI 4.0 signaling (RFC 1755 upd |
Done |
|
Submit IPv6 neighbor discovery, classical IP and NHRP MIBs, router-router NHRP, ATM UNI 4.0 signaling (RFC 1755 update), multicast server and broadcast for ATM, and NHRP for Frame Relay SVCs to the IESG. |
Done |
|
Publish the IP over ATM Framework document (now RFC 1932), submit the MARS draft to IESG as a Proposed Standard. |
Jan 98 |
|
Update for RFC1490 (to be submitted as Standard) |
Jan 98 |
|
Update for RFC1293 (to be submitted as Draft Standard) |
Feb 98 |
|
Submit IPv6 over NBMA, ATM, and FR drafts to IESG for consideration as a Proposed Standard. |
Feb 98 |
|
Submit Distributed MARS Service Using SCSP to IESG for consideration as an Informational RFC. |
Feb 98 |
|
Submit NHRP MIB to IESG for consideration as a Proposed Standard. |
Mar 98 |
|
Submit ILMI-Based Server Discovery for ATMARP to IESG for consideration as a Proposed Standard. |
Mar 98 |
|
Submit ILMI-Based Server Discovery for MARS to IESG for consideration as a Proposed Standard. |
Mar 98 |
|
Submit Intra-area Unicast based upon OSPF ARA to IESG for consideration as a Proposed Standard. |
Mar 98 |
|
Submit ILMI-Based Server Discovery for NHRP to IESG for consideration as a Proposed Standard. |
Mar 98 |
|
Submit Ion Security I-D to IESG for consideration as a Proposed Standard. |
Nov 98 |
|
NHRP client guidelines |
Nov 98 |
|
Use of Proxy PAR |
Nov 98 |
|
Router-Router NHRP |
Dec 98 |
|
CLOSE DOWN WORKING GROUP |
Internet-Drafts:
· Definitions of Managed Objects for the NBMA Next Hop Resolution Protocol (NHRP)
· Inverse Address Resolution Protocol
· NHRP for Destinations off the NBMA Subnetwork
· A Distributed ATMARP Service Using SCSP
· Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification
· Definitions of Managed Objects for Server Cache Synchronization Protocol Using SMIv2
· Multiprotocol Encapsulation over ATM Adaptation Layer 5
Request For Comments:
RFC |
Status |
Title |
RFC2121 |
Issues affecting MARS Cluster Size | |
RFC2149 |
Multicast Server Architectures for MARS-based ATM multicasting. | |
RFC2115 |
DS |
Management Information Base for Frame Relay DTEs Using SMIv2 |
RFC2226 |
PS |
IP Broadcast over ATM Networks |
RFC2269 |
Using the MARS model in non-ATM NBMA networks. | |
RFC2225 |
PS |
Classical IP and ARP over ATM |
RFC2320 |
PS |
Definitions of Managed Objects for Classical IP and ARP Over ATM Using SMIv2 (IPOA-MIB) |
RFC2333 |
PS |
NHRP Protocol Applicability Statement |
RFC2334 |
PS |
Server Cache Synchronization Protocol (SCSP) |
RFC2335 |
PS |
A Distributed NHRP Service Using SCSP |
RFC2331 |
PS |
ATM Signalling Support for IP over ATM - UNI Signalling 4.0 Update |
RFC2332 |
PS |
NBMA Next Hop Resolution Protocol (NHRP) |
RFC2337 |
E |
Intra-LIS IP multicast among routers over ATM using Sparse Mode PIM |
RFC2336 |
Classical IP to NHRP Transition | |
RFC2390 |
DS |
Inverse Address Resolution Protocol |
RFC2417 |
PS |
Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM Networks |
RFC2427 |
S |
Multiprotocol Interconnect over Frame Relay |
RFC2443 |
E |
A Distributed MARS Service Using SCSP |
RFC2491 |
PS |
IPv6 over Non-Broadcast Multiple Access (NBMA) networks |
RFC2492 |
PS |
IPv6 over ATM Networks |
RFC2520 |
E |
NHRP with Mobile NHCs |
RFC2583 |
Guidelines for Next Hop Client (NHC) Developers | |
RFC2590 |
PS |
Transmission of IPv6 Packets over Frame Relay Networks Specification |
RFC2601 |
PS |
ILMI-Based Server Discovery for ATMARP |
RFC2602 |
PS |
ILMI-Based Server Discovery for MARS |
RFC2603 |
PS |
ILMI-Based Server Discovery for NHRP |
None received.
None received.