Re: [manet] Start work: update draft for RFC5444-Packets

Joseph Macker <jpmacker@gmail.com> Mon, 23 July 2012 17:27 UTC

Return-Path: <jpmacker@gmail.com>
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 1CDE121F8642 for <manet@ietfa.amsl.com>; Mon, 23 Jul 2012 10:27:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level:
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_22=0.6, J_CHICKENPOX_46=0.6, RCVD_IN_DNSWL_LOW=-1]
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 o20VPLJPX7Lx for <manet@ietfa.amsl.com>; Mon, 23 Jul 2012 10:27:55 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9ECA421F865F for <manet@ietf.org>; Mon, 23 Jul 2012 10:27:55 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so5390474vbb.31 for <manet@ietf.org>; Mon, 23 Jul 2012 10:27:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=r7slIYcYyTXQ0HRh38iRZbO8m2/lnmlYUZEX//sptl8=; b=rrVhMtDR6Epf2OkGAUHoM+EykESGCRO6BJqwD+6cUbx8vU2VWwZNpM0ZPZlIBtD0x3 lLz/nmova9EjU/eyLsFcD+ai5r2hwYg8ucKXJ7rFBqF2B4r2PR+p2dXNwSWYr6PkGvZX 8sUw409FluQBIES9jAK1zWMtFebGyha51ZucT7WOKNLD93vv2JerzLOnl8dMwwmx+o9I QFzcGJ8oBqUxTc86mi/MKAs97H/lR8g/3X1+ESge5d92OHvYpFsS103+sXoOWaJLLqvC WPlSOgOXi7pn99UnvSdFuReACUR65ugP7QW+Up6527slXxErMrU6Iue1VNWcXBY6gBHL zucA==
MIME-Version: 1.0
Received: by 10.221.12.195 with SMTP id pj3mr13156370vcb.68.1343064474678; Mon, 23 Jul 2012 10:27:54 -0700 (PDT)
Received: by 10.58.200.97 with HTTP; Mon, 23 Jul 2012 10:27:54 -0700 (PDT)
In-Reply-To: <15E2F358-45A5-4E54-A5E3-E9D604446E39@cisco.com>
References: <SUKNPT8109i6YEFmsQS0000e21e@SUKNPT8109.cogent-dsn.local> <7B31B0093014224A843C10C0CCE92AC10467359C@SUKNPT8106.cogent-dsn.local> <302BB11B-A830-4AD7-AF05-728134C90A4F@thomasclausen.org> <6619DBF5-E3CD-4158-AECE-CFA6689C6CBD@cisco.com> <5D549284-A035-4393-8642-C8189E8171F7@cisco.com> <CAK=bVC_SX86kw8kP_A86z2YJOdx0bXBywuXe04t_qRsSQzphCA@mail.gmail.com> <15E2F358-45A5-4E54-A5E3-E9D604446E39@cisco.com>
Date: Mon, 23 Jul 2012 13:27:54 -0400
Message-ID: <CAHA-Tp7eNrXvHR5WSz_B-rL9RN89PYdsVJ6spdDYF0e8ui4VZg@mail.gmail.com>
From: Joseph Macker <jpmacker@gmail.com>
To: manet <manet@ietf.org>
Content-Type: multipart/alternative; boundary="bcaec54eeffcec746004c58290ee"
Subject: Re: [manet] Start work: update draft for RFC5444-Packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Mon, 23 Jul 2012 17:27:57 -0000

+1 also against this right now.

On Mon, Jul 23, 2012 at 1:16 PM, Bo Berry <boberry@cisco.com> wrote:

> +1, big agreement here!
>
> On Jul 23, 2012, at 1:10 PM, Ulrich Herberg wrote:
>
> > I don't see the need for updating RFC5444 at the moment.
> >
> > Best
> > Ulrich
> >
> > On Mon, Jul 23, 2012 at 8:00 AM, Stan Ratliff (sratliff) <
> sratliff@cisco.com> wrote:
> > +1
> >
> > Regards,
> > Stan
> >
> > On Jul 23, 2012, at 7:27 AM, Bo Berry wrote:
> >
> > > As a co-author of DLEP, I agree w/ Rick&Thomas.  We (DLEP authors) are
> > > working on DLEP revisions.
> > >
> > > -Bo
> > >
> > >
> > > On Jul 23, 2012, at 6:42 AM, Thomas Clausen wrote:
> > >
> > >> I agree with Rick, and want to add a few things ...
> > >>
> > >> On Jul 23, 2012, at 11:16 AM, Rick Taylor wrote:
> > >>
> > >>> Hi Abdussalam,
> > >>>
> > >>> I would recommend that you be very careful about attempting to
> > >>> adapt/extend RFC5444, particularly with respect to DLEP, because it
> is
> > >>> still open to debate whether any future DLEP draft will use RFC5444
> for
> > >>> its packet format, and I believe the authors are leaning away from
> it.
> > >>
> > >> Yes - plus, it is also not established yet that RFC5444 isn't
> appropriate for carrying DLEP signals (should the authors/WG go that way).
> > >>
> > >>> Also, there has been a lot of comment on this mailing list about not
> > >>> updating RFC5444 yet as there appears little consensus about the
> actual
> > >>> failings of the format w.r.t applicable protocols, i.e. all the
> > >>> 'complaints' about the format appear to be short-comings in the
> > >>> consuming protocols, not the packetBB format itself.
> > >>
> > >> +1
> > >>
> > >>> Can you perhaps outline what you see as the failings of RFC5444 here
> > >>> before you produce a lengthy document, in order to gather some quick
> > >>> peer-review comments, as many on this list struggle to find time to
> > >>> digest long formal drafts, and I wouldn't want you to suffer from
> TL;DR
> > >>> ('too-long; didn't-read').
> > >>
> > >> Even before that, it would be helpful to see a real routing protocol
> (which DLEP is not), with a real usecase & industry behind it (so, not just
> a thought experiment), with requirements pushed from real deployments (so,
> outside of a lab), which  is within the [manet] scope - and for which its
> signals cannot properly be expressed in RFC5444.
> > >>
> > >> Best,
> > >>
> > >> Thomas
> > >>
> > >>
> > >>> Rick Taylor
> > >>> Cassidian Systems
> > >>>
> > >>>> -----Original Message-----
> > >>>> From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On
> Behalf
> > >>> Of
> > >>>> Abdussalam Baryun
> > >>>> Sent: 21 July 2012 14:33
> > >>>> To: manet
> > >>>> Subject: [manet] Start work: update draft for RFC5444-Packets
> > >>>>
> > >>>> Hi
> > >>>>
> > >>>> I started working on a new draft to make some updates to the
> RFC5444,
> > >>>> so manet-packets can be more used by AODVv2, DLEP, and other
> possible
> > >>>> protocols.
> > >>>>
> > >>>> I will consider your input below of  the discussions regarding
> > >>>> 5444-packets, also in the past there was a request that there is a
> > >>>> need for how to use 5444, so this draft may include as well,
> > >>>>
> > >>>> http://www.ietf.org/mail-archive/web/manet/current/msg13212.html
> > >>>> http://www.ietf.org/mail-archive/web/manet/current/msg13105.html
> > >>>> http://www.ietf.org/mail-archive/web/manet/current/msg12430.html
> > >>>>
> > >>>> If you have any comment or advise to this started work please reply,
> > >>>>
> > >>>> AB
> > >>>> _______________________________________________
> > >>>> 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 mailing list
> > >> manet@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/manet
> > >
> > > ----
> > > boberry@cisco.com
> > > This email may contain confidential and privileged material for the
> sole use of the intended recipient. This email may contain information that
> is protected by NDA. Any unauthorized review, use, distribution or
> disclosure by others is strictly prohibited. If you are not the intended
> recipient (or authorized to receive for the recipient), please contact the
> sender by reply email and delete all copies of this message.
> > >
> > > _______________________________________________
> > > 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
> >
>
> ----
> boberry@cisco.com
> This email may contain confidential and privileged material for the sole
> use of the intended recipient. This email may contain information that is
> protected by NDA. Any unauthorized review, use, distribution or disclosure
> by others is strictly prohibited. If you are not the intended recipient (or
> authorized to receive for the recipient), please contact the sender by
> reply email and delete all copies of this message.
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>