Internetworking Over NBMA (ion) Concluded WG
Note: The data for concluded WGs is occasionally incorrect.
|WG||Name||Internetworking Over NBMA|
|Area||Internet Area (int)|
|Dependencies||Document dependency graph (SVG)|
Charter for Working Group
Note: This Working Group is jointly chartered by the Routing Area.
The Routing Area Director: Joel Halpern (firstname.lastname@example.org)
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.
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
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.
|Dec 1998||CLOSE DOWN WORKING GROUP|
|Nov 1998||Router-Router NHRP|
|Nov 1998||Use of Proxy PAR|
|Nov 1998||NHRP client guidelines|
|Mar 1998||Submit Ion Security I-D to IESG for consideration as a Proposed Standard.|
|Mar 1998||Submit ILMI-Based Server Discovery for NHRP to IESG for consideration as a Proposed Standard.|
|Mar 1998||Submit ILMI-Based Server Discovery for MARS to IESG for consideration as a Proposed Standard.|
|Mar 1998||Submit ILMI-Based Server Discovery for ATMARP to IESG for consideration as a Proposed Standard.|
|Mar 1998||Submit Intra-area Unicast based upon OSPF ARA to IESG for consideration as a Proposed Standard.|
|Feb 1998||Submit NHRP MIB to IESG for consideration as a Proposed Standard.|
|Feb 1998||Submit Distributed MARS Service Using SCSP to IESG for consideration as an Informational RFC.|
|Feb 1998||Submit IPv6 over NBMA, ATM, and FR drafts to IESG for consideration as a Proposed Standard.|
|Jan 1998||Update for RFC1293 (to be submitted as Draft Standard)|
|Jan 1998||Update for RFC1490 (to be submitted as Standard)|
|Done||Publish the IP over ATM Framework document (now RFC 1932), submit the MARS draft to IESG as a Proposed Standard.|
|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||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||IAB and IESG review of WG Status, and plans. This meeting will be scheduled to occur during SIGCOMM '96.|
|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||Begin work on internetworking over Frame Relay SVCs (RFC 1490 extension), using NHRP for address resolution.|