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)

Richard Ogier <ogier@earthlink.net> Mon, 03 June 2013 22:07 UTC

Return-Path: <ogier@earthlink.net>
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 AF1B421F861F for <ospf@ietfa.amsl.com>; Mon, 3 Jun 2013 15:07:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 nFPMT-XQkqF2 for <ospf@ietfa.amsl.com>; Mon, 3 Jun 2013 15:07:00 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by ietfa.amsl.com (Postfix) with ESMTP id 2258F11E80F4 for <ospf@ietf.org>; Mon, 3 Jun 2013 15:02:28 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=kStFFcjJOelzND2xM1S2vvv20hQpBDJx3Swxrf23MQveRehil510ja0hjjYj8fOW; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [71.128.200.145] (helo=[192.168.0.3]) by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <ogier@earthlink.net>) id 1Ujcpf-0005kf-2B; Mon, 03 Jun 2013 18:02:28 -0400
Message-ID: <51AD1275.30406@earthlink.net>
Date: Mon, 03 Jun 2013 15:02:29 -0700
From: Richard Ogier <ogier@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "<thomas.r.henderson@boeing.com>" <thomas.r.henderson@boeing.com>
References: <94A203EA12AECE4BA92D42DBFFE0AE4711038C@eusaamb101.ericsson.se> <94A203EA12AECE4BA92D42DBFFE0AE471103F0@eusaamb101.ericsson.se> <758141CC3D829043A8C3164DD3D593EA2EA6C32458@XCH-NW-16V.nw.nos.boeing.com>
In-Reply-To: <758141CC3D829043A8C3164DD3D593EA2EA6C32458@XCH-NW-16V.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: a073897a9455599e74bf435c0eb9d478e549f294dc8ae39d43997510a9f083d1478b19569c7702ea350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 71.128.200.145
Cc: 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: Mon, 03 Jun 2013 22:07:15 -0000

Tom,

Thanks for your review and comments. I added a motivating paragraph as 
you suggested, and submitted the revised draft:

http://www.ietf.org/id/draft-ietf-ospf-manet-single-hop-mdr-03.txt

Richard

On 6/1/2013 3:28 PM, Henderson, Thomas R wrote:
>> 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
>
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2242 / Virus Database: 3184/5876 - Release Date: 06/02/13
>
>
>