Re: [OSPF] Single Hop MANET versus Broadcast/P2MP Hybrid Interface
"Retana, Alvaro" <alvaro.retana@hp.com> Thu, 12 May 2011 17:10 UTC
Return-Path: <alvaro.retana@hp.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCE5BE06C8 for <ospf@ietfa.amsl.com>; Thu, 12 May 2011 10:10:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ANzJNnNsZ6fV for <ospf@ietfa.amsl.com>; Thu, 12 May 2011 10:10:57 -0700 (PDT)
Received: from g6t0186.atlanta.hp.com (g6t0186.atlanta.hp.com [15.193.32.63]) by ietfa.amsl.com (Postfix) with ESMTP id 4363CE0688 for <ospf@ietf.org>; Thu, 12 May 2011 10:10:57 -0700 (PDT)
Received: from G6W1798G.americas.hpqcorp.net (g6w1798g.atlanta.hp.com [16.230.17.175]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g6t0186.atlanta.hp.com (Postfix) with ESMTPS id DEF5D2C5EB; Thu, 12 May 2011 17:10:56 +0000 (UTC)
Received: from G1W1916.americas.hpqcorp.net (16.236.60.246) by G6W1798G.americas.hpqcorp.net (16.230.17.175) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 12 May 2011 17:09:25 +0000
Received: from GVW1338EXA.americas.hpqcorp.net ([16.236.29.11]) by G1W1916.americas.hpqcorp.net ([16.236.60.246]) with mapi; Thu, 12 May 2011 17:09:24 +0000
From: "Retana, Alvaro" <alvaro.retana@hp.com>
To: Acee Lindem <acee.lindem@ericsson.com>, OSPF List <ospf@ietf.org>
Date: Thu, 12 May 2011 17:09:21 +0000
Thread-Topic: [OSPF] Single Hop MANET versus Broadcast/P2MP Hybrid Interface
Thread-Index: AcwQKesEH1ZtPkRLTmCv11x5NDBn1wAnSOfw
Message-ID: <24646CE17826CF4A8DF71F9856C7E6565924402353@GVW1338EXA.americas.hpqcorp.net>
References: <B072BEDD-793D-4BC5-8227-BBB37F1D56D2@ericsson.com>
In-Reply-To: <B072BEDD-793D-4BC5-8227-BBB37F1D56D2@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [OSPF] Single Hop MANET versus Broadcast/P2MP Hybrid Interface
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2011 17:10:58 -0000
1. Yes. 2. Yes, but...IMHO we don't need a full refresh of the RFCs. An ID updating the RFC should be enough. The ID should be Experimental (just like the RFC). Alvaro. > -----Original Message----- > From: ospf-bounces@ietf.org [mailto:ospf-bounces@ietf.org] On Behalf Of > Acee Lindem > Sent: Wednesday, May 11, 2011 6:22 PM > To: OSPF List > Subject: [OSPF] Single Hop MANET versus Broadcast/P2MP Hybrid Interface > > Speaking as WG Co-Chair, > > As many of you remember, we spent a lot of WG time 2004-2007 discussing > various OSPF MANET solutions. We were unable to converge on a single > solution and ended up with 3 experimental RFCs. It was thought that > possibly one day a clear winner would emerge and become a standard. > While this may still happen in the future, I don't believe we are there > yet and do not feel it would be beneficial to renew the debate. > > In Beijing, the hybrid broadcast/P2MP interface was proposed with a > radio networks being one of the target environment. This collision with > the former work on OSPF MANET elicited much discussion. In Prague, the > chairs, authors, and some other interested parties met to specifically > address this collision. What we agreed was that the existing OSPF MANET > RFCs were the agreed upon solution(s) for MANET environments. The OSPF > hybrid interface could still be valuable as a simple adjacency > reduction technique on links where broadcast capability was available > but not all the links had the same costs. We also agreed that the OSPF > MANET mechanisms (with some simplifications) could also handle the > single hop case. > > Hence, the questions for the WG are: > > > 1. Do we want to accept draft-nsheth-ospf-hybrid-bcast-and-p2mp- > 01.txt as a WG document? > > https://datatracker.ietf.org/doc/draft-nsheth-ospf-hybrid-bcast-and- > p2mp > > 2. Do we wish to allow revisions of the OSPF MANET experimental RFCs > to cover the single-hop case (and possibly minor corrections)? > > https://datatracker.ietf.org/doc/rfc5449/ > https://datatracker.ietf.org/doc/rfc5614/ > https://datatracker.ietf.org/doc/rfc5820/ > > Note that IPR statements are filed for some of the above. > > Thanks, > Acee > > > > _______________________________________________ > OSPF mailing list > OSPF@ietf.org > https://www.ietf.org/mailman/listinfo/ospf
- [OSPF] Single Hop MANET versus Broadcast/P2MP Hyb… Acee Lindem
- Re: [OSPF] Single Hop MANET versus Broadcast/P2MP… John E Drake
- Re: [OSPF] Single Hop MANET versus Broadcast/P2MP… Richard Ogier
- Re: [OSPF] Single Hop MANET versus Broadcast/P2MP… Retana, Alvaro
- Re: [OSPF] Single Hop MANET versus Broadcast/P2MP… Alia Atlas
- Re: [OSPF] Single Hop MANET versus Broadcast/P2MP… Henderson, Thomas R
- Re: [OSPF] Single Hop MANET versus Broadcast/P2MP… Emmanuel Baccelli
- Re: [OSPF] Single Hop MANET versus Broadcast/P2MP… Stan Ratliff