Re: [OSPF] OSPF WG Last Call: Use of OSPF-MDR in Single-Hop Broadcast Networks - draft-ietf-ospf-manet-single-hop-mdr-01.txt (Corrected)

"Henderson, Thomas R" <thomas.r.henderson@boeing.com> Sat, 01 June 2013 22:29 UTC

Return-Path: <thomas.r.henderson@boeing.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 130FF21F992A for <ospf@ietfa.amsl.com>; Sat, 1 Jun 2013 15:29:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lH5FNbxR6Fg9 for <ospf@ietfa.amsl.com>; Sat, 1 Jun 2013 15:29:00 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) by ietfa.amsl.com (Postfix) with ESMTP id 4D96021F8DDD for <ospf@ietf.org>; Sat, 1 Jun 2013 15:28:58 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r51MSvRM017751 for <ospf@ietf.org>; Sat, 1 Jun 2013 17:28:58 -0500
Received: from XCH-NWHT-02.nw.nos.boeing.com (xch-nwht-02.nw.nos.boeing.com [130.247.70.248]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r51MSucd017748 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Sat, 1 Jun 2013 17:28:57 -0500
Received: from XCH-NW-16V.nw.nos.boeing.com ([130.247.25.238]) by XCH-NWHT-02.nw.nos.boeing.com ([130.247.70.248]) with mapi; Sat, 1 Jun 2013 15:28:56 -0700
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "'Acee Lindem'" <acee.lindem@ericsson.com>, "'rich.ogier@earthlink.net'" <rich.ogier@earthlink.net>
Date: Sat, 1 Jun 2013 15:28:56 -0700
Thread-Topic: [OSPF] OSPF WG Last Call: Use of OSPF-MDR in Single-Hop Broadcast Networks - draft-ietf-ospf-manet-single-hop-mdr-01.txt (Corrected)
Thread-Index: AQHOM8MykpZnRxb3wUyTsZ0rU2D/MZkhxU8Q
Message-ID: <758141CC3D829043A8C3164DD3D593EA2EA6C32458@XCH-NW-16V.nw.nos.boeing.com>
References: <94A203EA12AECE4BA92D42DBFFE0AE4711038C@eusaamb101.ericsson.se> <94A203EA12AECE4BA92D42DBFFE0AE471103F0@eusaamb101.ericsson.se>
In-Reply-To: <94A203EA12AECE4BA92D42DBFFE0AE471103F0@eusaamb101.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: OSPF List <ospf@ietf.org>
Subject: Re: [OSPF] OSPF WG Last Call: Use of OSPF-MDR in Single-Hop Broadcast Networks - draft-ietf-ospf-manet-single-hop-mdr-01.txt (Corrected)
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: Sat, 01 Jun 2013 22:29:05 -0000

> All, 
>
> I'd like to start a 3 week WG last call on the subject document. The last call will end at 
> 12:00 AM PDT on April 29th, 2012. Please review the document and send any comments to the 
> list prior to that time. Here is a URL for your convenience: 
> 
> https://datatracker.ietf.org/doc/draft-ietf-ospf-manet-single-hop-mdr/

Acee and Richard,
I realize that WGLC has passed on this draft, but I recently reviewed the latest (-02) version of this draft and had a few comments:

- I did not perceive any technical problems; however, I have not implemented or tested it
- the capability supports an important use case for OSPF MDR, and I think the section 2 guidance will be helpful to experimenters
- I think the draft could be (optionally) improved for readers with an additional motivating statement, along the lines of what is stated in RFC 6845.  Perhaps something at the bottom of page 1 like: "The rationale for using this interface type for single-hop broadcast networks, instead of a broadcast interface type, is to represent the underlying network in a point-to-multipoint manner, to allow finer granularity of neighbor cost settings.  In this sense, this document shows how the OSPF MDR interface type can be configured to provide the same kind of interface as specified in [RFC6845]." 

Overall, it seems to be ready to publish.

- Tom