Re: draft rolc minutes

dhc2@gte.com Mon, 24 July 1995 18:29 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10996; 24 Jul 95 14:29 EDT
Received: from nexen.nexen.com by IETF.CNRI.Reston.VA.US id aa10992; 24 Jul 95 14:29 EDT
Received: from maelstrom.acton.timeplex.com (maelstrom.nexen.com [204.249.97.5]) by nexen.nexen.com (8.6.12/8.6.12) with ESMTP id OAA06576; Mon, 24 Jul 1995 14:15:11 -0400
Received: (from root@localhost) by maelstrom.acton.timeplex.com (8.6.12/8.6.12) id OAA12029 for rolc-out; Mon, 24 Jul 1995 14:14:05 -0400
Received: from nexen.nexen.com (nexen.nexen.com [204.249.96.18]) by maelstrom.acton.timeplex.com (8.6.12/8.6.12) with ESMTP id OAA12020 for <rolc@nexen.com>; Mon, 24 Jul 1995 14:14:02 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: dhc2@gte.com
Received: from ns.gte.com ([132.197.8.9]) by nexen.nexen.com (8.6.12/8.6.12) with ESMTP id OAA06560 for <rolc@nexen.com>; Mon, 24 Jul 1995 14:14:01 -0400
Received: from minuteman.gte.com by ns.gte.com (8.6.10/8.6.10) id NAA27260; Mon, 24 Jul 1995 13:56:49 -0400
Received: by minuteman.gte.com (5.0/SMI-SVR4) id AA05464; Mon, 24 Jul 1995 14:00:41 -0400
Date: Mon, 24 Jul 1995 14:00:41 -0400
Message-Id: <9507241800.AA05464@minuteman.gte.com>
To: dhc2@gte.com, yakov@cisco.com
Cc: rolc@nexen.com
Subject: Re: draft rolc minutes
Content-Length: 1373
X-Orig-Sender: owner-rolc@nexen.com
Precedence: bulk
X-Info: Submissions to rolc@nexen.com
X-Info: [Un]Subscribe requests to rolc-request@nexen.com
X-Info: Archives for rolc via ftp://ietf.cnri.reston.va.us/ietf-mail-archive/rolc/

<<> I agree with the idea of removing IP Encapsulation. The benefits
<<> of removing IP encapsulation e.g., simplifying the operation,
<<> protocol independence, better support for MPOA and providing
<<> a better working ground for the router-router case outweight
<<> the benefit of retaining IP encapsulation, ie Server Mode.
<<
<<I'd like to understand how removing IP Encapsulation provides
<<"a better working ground for the router-router" case.
<<
<<Yakov.

Removing IP encapsulation virtually implies that all the routers
in the NBMA cloud be NHRP speakers. Otherwise, the use of NHRP 
would be limited , in that as soon as your NHRP request hits a non-NHRP
speaker, it is dropped. Then, in a "homogeneous" NHRP environment,
your proposals number 1 and number 2, which require that routers
in the short cut path propagate topology changes information
can be implemented more easily. As you pointed out, when there are
non-NHRP speaking routers in the short-cut path, additional measures
should be taken. I used the term "better working ground" to mean that
fabric mode provides a more flexible environment towards the implementation
of some of your proposals. 

Having said that, among the proposals by you and Bruce, I like the 3rd 
one the most. Conceptually, it is simple. Also, it is more general in 
that it will detect a loop regardless of its cause.

Derya