[manet] Updating or replacing RFC 3626
"Adrian Farrel" <adrian@olddog.co.uk> Fri, 08 June 2012 19:57 UTC
Return-Path: <adrian@olddog.co.uk>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00BDD11E80EF for <manet@ietfa.amsl.com>; Fri, 8 Jun 2012 12:57:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.488
X-Spam-Level:
X-Spam-Status: No, score=-2.488 tagged_above=-999 required=5 tests=[AWL=0.110, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 vZR5lkGpQe-Q for <manet@ietfa.amsl.com>; Fri, 8 Jun 2012 12:57:38 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id B776611E80B0 for <manet@ietf.org>; Fri, 8 Jun 2012 12:57:26 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q58JvP4e024816 for <manet@ietf.org>; Fri, 8 Jun 2012 20:57:25 +0100
Received: from 950129200 (ns-visitor-nsrp.juniper.net [208.223.208.242]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q58JvKYk024789 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <manet@ietf.org>; Fri, 8 Jun 2012 20:57:22 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'manet' <manet@ietf.org>
Date: Fri, 08 Jun 2012 20:57:18 +0100
Message-ID: <001901cd45b0$ea911630$bfb34290$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_001A_01CD45B9.4C7BA3D0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac1FsOesZUVwhxvISFuDzvMTppSUlg==
Content-Language: en-gb
Subject: [manet] Updating or replacing RFC 3626
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 19:57:39 -0000
PMFJI This thread has brought up a question that I need to ask as I review OLSRv2 which you have requested goes for publication. In what way does the WG intend OLSRv2 to replace/update/deprecate OSLRv1? There is a whole range of options, and what you choose depends largely on what future exposure you think OLSRv1 should have. You could: - Move RFC 3626 to Historic - Obsolete RFC 3626 with OLSRv2 - Leave RFC 3626 in place for further experimentation - Update RFC 3626 as a separate activity to advance the experiment What I don't think you are doing with OLSRv2 is Updating RFC 3626. Thanks, Adrian From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Stan Ratliff Sent: 08 June 2012 19:34 To: Teco Boot Cc: Dearlove, Christopher (UK); manet; Abdussalam Baryun Subject: Re: [manet] There is no document submitted so far to WG stating an update request for RFC3626 Abdussalam, The first paragraph of the "Introduction" section of OSLRv2 states: "The Optimized Link State Routing protocol version 2 (OLSRv2) is the successor to OLSR (version 1) as published in [RFC3626]." As such, I'm assuming that no additional work to RFC 3626 is expressed or implied - OLSRv1 is documented in RFC 3626; OLSRv2 is, for all intents and purposes, a new protocol documented by this new RFC. Regards, Stan On Jun 8, 2012, at 2:13 PM, Teco Boot wrote: Op 8 jun. 2012 om 19:25 heeft Abdussalam Baryun <abdussalambaryun@gmail.com> het volgende geschreven: Hi Teco, More precisely, we work on a replacement for the initial experimental version. you mean that there is a work for replacement, I don't see any discussion befor about that, please advise, I guess you can find it in the archives. RFC 3626 is not updated. It could get historic one day. same what I thought, but one author of OLSRv2 mentioned that I may misunderstood the process of OLSRv2, even though the authors don't specify what will happen to RFC3626 when OLSRv2 is an RFC. I seen other I-D when submitted for IESG they put inside the draft what the draft authors intention if they obslete another documents or if their new draft is updating any thing, I have confidence in authors' knowledge on the proces. Dito for chairs. OLSRv2 does not mention the process of update, which IMHO it should if authors want to update RFC3626, I believe they don't. Same for workgroup. I may be wrong, but I hope the chair updates me with the status, may be he received a private request of update out of the discussion list, please advise, I guess you misunderstood him. Enjoy your weekend. Teco Regards AB +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ On 6/8/12, Teco Boot <teco@inf-net.nl> wrote: Op 8 jun. 2012, om 14:31 heeft Henning Rogge het volgende geschreven: On Fri, Jun 8, 2012 at 1:44 PM, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote: Hi Chris, Please note that MANET WG is doing OLSRv2 without updating RFC3626 which make people think why? This sentence doesn't make sense. OLSRv2 IS the update of RFC 3626. More precisely, we work on a replacement for the initial experimental version. RFC 3626 is not updated. It could get historic one day. Teco Are you sure you understand how the IETF works to update existing protocols? Henning Rogge -- Steven Hawkings about cosmic inflation: "An increase of billions of billions of percent in a tiny fraction of a second. Of course, that was before the present government." _______________________________________________ manet mailing list manet@ietf.org https://www.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www.ietf.org/mailman/listinfo/manet
- [manet] Updating or replacing RFC 3626 Adrian Farrel
- Re: [manet] Updating or replacing RFC 3626 Stan Ratliff
- Re: [manet] Updating or replacing RFC 3626 Henning Rogge
- Re: [manet] Updating or replacing RFC 3626 Thomas Heide Clausen
- Re: [manet] Updating or replacing RFC 3626 Ulrich Herberg
- Re: [manet] Updating or replacing RFC 3626 Teco Boot
- Re: [manet] Updating or replacing RFC 3626 Thomas Heide Clausen
- Re: [manet] Updating or replacing RFC 3626 Stan Ratliff
- Re: [manet] Updating or replacing RFC 3626 Adrian Farrel
- Re: [manet] Updating or replacing RFC 3626 Teco Boot
- Re: [manet] Updating or replacing RFC 3626 Henning Rogge
- Re: [manet] Updating or replacing RFC 3626 Teco Boot
- Re: [manet] Updating or replacing RFC 3626 Abdussalam Baryun
- Re: [manet] Updating or replacing RFC 3626 Dearlove, Christopher (UK)
- Re: [manet] Updating or replacing RFC 3626 Philippe Jacquet
- Re: [manet] Updating or replacing RFC 3626 Abdussalam Baryun
- [manet] FW: Updating or replacing RFC 3626 Dr John P Mullen
- Re: [manet] FW: Updating or replacing RFC 3626 Teco Boot