Re: [DMM] conclusion of adoption calls

Thierry Ernst <thierry.ernst@inria.fr> Sat, 09 January 2016 11:57 UTC

Return-Path: <thierry.ernst@inria.fr>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8B9E1A7113 for <dmm@ietfa.amsl.com>; Sat, 9 Jan 2016 03:57:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.95
X-Spam-Level:
X-Spam-Status: No, score=-0.95 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, J_CHICKENPOX_56=0.6] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t9KD3mFraQhB for <dmm@ietfa.amsl.com>; Sat, 9 Jan 2016 03:56:58 -0800 (PST)
Received: from jiboia.ensmp.fr (jiboia.ensmp.fr [194.214.158.137]) by ietfa.amsl.com (Postfix) with ESMTP id 36AF71A710D for <dmm@ietf.org>; Sat, 9 Jan 2016 03:56:57 -0800 (PST)
Received: from [192.168.1.26] (vir78-2-82-247-222-224.fbx.proxad.net [82.247.222.224]) (authenticated bits=0) by jiboia.ensmp.fr (8.15.2/8.15.1/JMMC-22/Oct/2013) with ESMTPSA id u09BusJj007911 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO) for <dmm@ietf.org>; Sat, 9 Jan 2016 12:56:56 +0100
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Thierry Ernst <thierry.ernst@inria.fr>
In-Reply-To: <CAC8QAceh4Pwik9ayCjUQ-aL6RWxGfZYCKp-350bNMhWxYZy8qw@mail.gmail.com>
Date: Sat, 09 Jan 2016 12:56:52 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C4F5A928-7111-4026-B989-6BD6551A7A03@inria.fr>
References: <56719207.7000604@gmail.com> <1450439102.11602.25.camel@it.uc3m.es> <CAC8QAccjPjfbn_f4-ECh3CuB+-M9OmjZATcchyLUaqB15MFZ2w@mail.gmail.com> <73AFD314-B981-429A-B6A8-F8F906AB60D6@gmail.com> <568FB180.1000905@gmail.com> <1093D79B-3CE8-4EC5-AE2B-C345018C5AC6@inria.fr> <568FE65C.4020008@gmail.com> <CAC8QAcfp=njXS=7EpMvoTqpq9P-8LHGnB0cQu=6S9rVm53ORdQ@mail.gmail.com> <58A5EBFF-CD12-4F4A-BE55-57FF9BB65E5D@gmail.com> <CAC8QAceh4Pwik9ayCjUQ-aL6RWxGfZYCKp-350bNMhWxYZy8qw@mail.gmail.com>
To: dmm@ietf.org
X-Mailer: Apple Mail (2.2104)
X-Miltered: at jiboia.ensmp.fr with ID 5690F586.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Auth: USER-ID thierry.ernst
X-j-chkmail-Enveloppe: 5690F586.000 from vir78-2-82-247-222-224.fbx.proxad.net/vir78-2-82-247-222-224.fbx.proxad.net/82.247.222.224/[192.168.1.26]/<thierry.ernst@inria.fr>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dmm/xkh8FyrIzAPI9Cy1EJYcOnvWaRo>
Subject: Re: [DMM] conclusion of adoption calls
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jan 2016 11:57:00 -0000

What are protocols you think no one uses ? 

MIPv6 and NEMOv6 needs maintenance, and probably more than than maintenance. 

Regards,
Thierry Ernst.


> Le 8 janv. 2016 à 20:48, Behcet Sarikaya <sarikaya2012@gmail.com> a écrit :
> 
> On Fri, Jan 8, 2016 at 12:34 PM, Jouni.nosmap <jouni.nospam@gmail.com> wrote:
>> Well one can always pursue ISE/AD sponsored track if one so feels like.
>> 
>> Just saying there are options..  if one desires to go through the WG process DMM has provisions for Mobile IPv6 protocol family maintenance work.
>> 
> 
> I started this thread by stating that:
> 
> Let me ask what is the point in maintaining the protocols that no one uses?
> For academic purposes? If yes, then they should find their places in
> the conferences or journals.
> 
> No one objected to the first point.
> 
> So what is the justification for maintenance? As I said before,
> charter items can be changed or they do not have to be used.
> 
> Behcet
>> Jouni
>> 
>> Sent from a smart phone.. Mind the typos..
>> 
>>> Behcet Sarikaya <sarikaya2012@gmail.com> kirjoitti 8.1.2016 kello 9.15:
>>> 
>>>> On Fri, Jan 8, 2016 at 10:39 AM, Jouni Korhonen <jouni.nospam@gmail.com> wrote:
>>>> 
>>>> As Sri pointed out DMM is OK to work on "maintenance-oriented extensions of
>>>> the Mobile IPv6 protocol family". So this is likely the venue within IETF.
>>>> Mobile IPv4 as such has no place here.
>>> 
>>> 
>>> Why not ISE? For both MIPv6 and MIPv4.
>>> Of course you may not be able modify existing RFCs but just write it
>>> as a new draft and do not bother dmm where future protocol work is
>>> supposed to be done.
>>> 
>>> Behcet
>>> 
>>>> - Jouni
>>>> 
>>>> 
>>>> 1/8/2016, 6:50 AM, Thierry Ernst kirjoitti:
>>>>> 
>>>>> 
>>>>> Hi Alex, all,
>>>>> 
>>>>> My understanding of what Jouni wrote is that it’s fine to work on MIP6
>>>>> improvement, but the MIP4 can live its life as is, to which I totally agree.
>>>>> And I also agree with Alex that we need to fix bugs in MIP6 (and the related
>>>>> suite, in particular NEMO) and progress them in the standard track. It has
>>>>> been too long since we last work on those and now it is certainly right to
>>>>> do it.
>>>>> 
>>>>> So, the question is if DMM is the right place or not to do the work, if
>>>>> not I would like to hear about alternatives within the IETF.
>>>>> 
>>>>> Regards,
>>>>> Thierry.
>>>>> 
>>>>> 
>>>>> 
>>>>>> Le 8 janv. 2016 à 13:54, Alexandre Petrescu
>>>>>> <alexandre.petrescu@gmail.com> a écrit :
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Le 22/12/2015 04:56, Jouni a écrit :
>>>>>>> 
>>>>>>> 
>>>>>>> Behcet,
>>>>>>> 
>>>>>>> Thank you for your constructive comments. I believe academic
>>>>>>> conferences/journals are not appropriate venues for PMIPv6/MIPv6
>>>>>>> maintenance since these protocol families are already past their
>>>>>>> prime time as “hot research topics". Looking at the existing charter
>>>>>>> I cannot find too much love towards anything IPv4 so I think we can
>>>>>>> let MIPv4 finally rest in peace.
>>>>>> 
>>>>>> 
>>>>>> Jouni I can agree with you in general.
>>>>>> 
>>>>>> But let me suggest that MIPv4 and MIPv6 are two implementations very
>>>>>> important in some places including where I work.
>>>>>> 
>>>>>> They are no longer 'hot' as you say, but there are certainly protocol and
>>>>>> implementation bugs which need correction.  Actually some of the corrections
>>>>>> have already been applied but are not reflected in RFCs.
>>>>>> 
>>>>>> Sometimes there is a feeling of frustration if implementations thrive
>>>>>> where WG cares little.
>>>>>> 
>>>>>> <provocative> a widespread implementation of MIP6 is still bugged and
>>>>>> does not respect the MIPv6 RFC - do you want that discussed
>>>>>> publicly?</provocative>.
>>>>>> 
>>>>>> Alex
>>>>>> 
>>>>>>> 
>>>>>>> - Jouni
>>>>>>> 
>>>>>>> 
>>>>>>>> On 21 Dec 2015, at 09:46, Behcet Sarikaya <sarikaya2012@gmail.com>
>>>>>>>> wrote:
>>>>>>>> 
>>>>>>>> Hi Jouni, all,
>>>>>>>> 
>>>>>>>> Let me ask what is the point in maintaining the protocols that no
>>>>>>>> one uses? For academic purposes? If yes, then they should find
>>>>>>>> their places in the conferences or journals.
>>>>>>>> 
>>>>>>>> Now, mip4 WG has been closed. So is dmm going to maintain mip4 as
>>>>>>>> well?
>>>>>>>> 
>>>>>>>> Regards,
>>>>>>>> 
>>>>>>>> Behcet
>>>>>>>> 
>>>>>>>> On Fri, Dec 18, 2015 at 5:45 AM, Carlos Jesús Bernardos Cano
>>>>>>>> <cjbc@it.uc3m.es> wrote:
>>>>>>>>> 
>>>>>>>>> Hi Jouni, all,
>>>>>>>>> 
>>>>>>>>> Although I'm already late, I just wanted to express my
>>>>>>>>> post-adoption call to the three drafts.
>>>>>>>>> 
>>>>>>>>> Carlos
>>>>>>>>> 
>>>>>>>>>> On Wed, 2015-12-16 at 08:32 -0800, Jouni Korhonen wrote:
>>>>>>>>>> 
>>>>>>>>>> Folks,
>>>>>>>>>> 
>>>>>>>>>> The WG adoption call for all three I-Ds have completed:
>>>>>>>>>> draft-gundavelli-dmm-lma-controlled-mag-params-00
>>>>>>>>>> draft-yan-dmm-hnprenum-03 draft-seite-dmm-rg-multihoming-02
>>>>>>>>>> 
>>>>>>>>>> The adoption for the first two was unanimous. The last
>>>>>>>>>> (draft-seita- *) received few concerns but the number of
>>>>>>>>>> supporters was enough to convince the chairs there is enough
>>>>>>>>>> interest and support to work on it. The chairs encourage the
>>>>>>>>>> authors of draft-seite-* to pay close attention and work out
>>>>>>>>>> the concerns raised during the adoption call.
>>>>>>>>>> 
>>>>>>>>>> For the I-D authors. Please, submit draft-ietf-*-00 versions of
>>>>>>>>>> the documents as soon as possible.
>>>>>>>>>> 
>>>>>>>>>> - Jouni & Dapeng
>>>>>>>>>> 
>>>>>>>>>> _______________________________________________ dmm mailing
>>>>>>>>>> list dmm@ietf.org https://www.ietf.org/mailman/listinfo/dmm
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> _______________________________________________ dmm mailing list
>>>>>>>>> dmm@ietf.org https://www.ietf.org/mailman/listinfo/dmm
>>>>>>> 
>>>>>>> 
>>>>>>> _______________________________________________ dmm mailing list
>>>>>>> dmm@ietf.org https://www.ietf.org/mailman/listinfo/dmm
>>>>>> 
>>>>>> _______________________________________________
>>>>>> dmm mailing list
>>>>>> dmm@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/dmm
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> dmm mailing list
>>>>> dmm@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/dmm
>>>> 
>>>> _______________________________________________
>>>> dmm mailing list
>>>> dmm@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/dmm