| < draft-ietf-isis-wg-mesh-group-00.txt | draft-ietf-isis-wg-mesh-group-01.txt > | |||
|---|---|---|---|---|
| Internet Engineering Task Force R. Balay | Internet Engineering Task Force R. Balay | |||
| INTERNET DRAFT Ericsson | INTERNET DRAFT Ericsson | |||
| D. Katz | D. Katz | |||
| Juniper Networks | Juniper Networks | |||
| J. Parker | J. Parker | |||
| Lucent Technology | Lucent Technology | |||
| Feb 21, 2000 | July 7, 2000 | |||
| IS-IS Mesh Groups | IS-IS Mesh Groups | |||
| <draft-ietf-isis-wg-mesh-group-00.txt> | <draft-ietf-isis-wg-mesh-group-01.txt> | |||
| 1. Status of this Memo | 1. Status of this Memo | |||
| This document is an Internet-Draft and is in full conformance | This document is an Internet-Draft and is in full conformance | |||
| with all provisions of Section 10 of RFC 2026. | with all provisions of Section 10 of RFC 2026. | |||
| Internet-Drafts are working documents of the Internet | Internet-Drafts are working documents of the Internet | |||
| Engineering Task Force (IETF), its areas, and its working | Engineering Task Force (IETF), its areas, and its working | |||
| groups. Note that other groups may also distribute working | groups. Note that other groups may also distribute working | |||
| documents as Internet-Drafts. | documents as Internet-Drafts. | |||
| skipping to change at page 2, line ? ¶ | skipping to change at page 2, line ? ¶ | |||
| with implementations that do not support this feature. | with implementations that do not support this feature. | |||
| This document is provided to the IETF working group on IS-IS. | This document is provided to the IETF working group on IS-IS. | |||
| Table of Contents | Table of Contents | |||
| 1. Status of this Memo.................................. 1 | 1. Status of this Memo.................................. 1 | |||
| 2. Abstract............................................. 2 | 2. Abstract............................................. 2 | |||
| 3. Overview............................................. 2 | 3. Overview............................................. 2 | |||
| 4. Definitions of Mesh Groups........................... 4 | 4. Definitions of Mesh Groups........................... 4 | |||
| 5. Drawbacks of Mesh Groups............................. 5 | 5. Drawbacks of Mesh Groups............................. 6 | |||
| 6. Interoperation with Mesh Groups...................... 7 | 6. Interoperation with Mesh Groups...................... 7 | |||
| 7. Acknowledgments...................................... 7 | 7. Acknowledgments...................................... 7 | |||
| 8. References........................................... 7 | 8. References........................................... 7 | |||
| 9. Security Considerations.............................. 7 | 9. Security Considerations.............................. 8 | |||
| 10. Authors' Address..................................... 8 | 10. Authors' Address..................................... 8 | |||
| 11. Full Copyright Statement............................. 9 | 11. Full Copyright Statement............................. 9 | |||
| 3. Overview | 3. Overview | |||
| In ATM or frame relay networks Intermediate Systems are | In ATM or frame relay networks Intermediate Systems are | |||
| inter-connected using virtual circuits (VCs) which are logical | inter-connected using virtual circuits (VCs) which are logical | |||
| point-to-point links. Some organizations attach multiple | point-to-point links. Some organizations attach multiple | |||
| Intermediate Systems to form a full "mesh" topology, where | Intermediate Systems to form a full "mesh" topology, where | |||
| every pair of Intermediate Systems are connected by a point- | every pair of Intermediate Systems are connected by a point- | |||
| skipping to change at page 8, line 12 ¶ | skipping to change at page 8, line 12 ¶ | |||
| Connectionless-mode Network Service (ISO 8473)", June | Connectionless-mode Network Service (ISO 8473)", June | |||
| 1992. | 1992. | |||
| 9. Security Considerations | 9. Security Considerations | |||
| This document raises no new security issues for IS-IS. | This document raises no new security issues for IS-IS. | |||
| 10. Authors' Address | 10. Authors' Address | |||
| Rajesh Balay | Rajesh Balay | |||
| Ericsson IP Infrastructure, Inc. | CoSine Communications | |||
| 920 Main Campus Drive, Suite 500 | 1200 Bridge Parkway | |||
| Raleigh, NC 27606 | Redwood City, CA 94065 | |||
| email: balay@torrentnet.com | email: Rajesh.Balay@cosinecom.com | |||
| Dave Katz | Dave Katz | |||
| Juniper Networks | Juniper Networks | |||
| 385 Ravendale Drive | 385 Ravendale Drive | |||
| Mountain View, CA 94043 | Mountain View, CA 94043 | |||
| email: dkatz@juniper.net | email: dkatz@juniper.net | |||
| Jeff Parker | Jeff Parker | |||
| Lucent Technologies, | Lucent Technologies, | |||
| 200 Nickerson Road, | 200 Nickerson Road, | |||
| End of changes. 5 change blocks. | ||||
| 8 lines changed or deleted | 8 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||