Re: [Pce] Experimental Codepoints allocation in PCEP registry

Dhruv Dhody <dhruv.dhody@huawei.com> Thu, 16 June 2016 05:26 UTC

Return-Path: <dhruv.dhody@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A31112D1A9 for <pce@ietfa.amsl.com>; Wed, 15 Jun 2016 22:26:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Level:
X-Spam-Status: No, score=-5.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 311_xgwkfuS9 for <pce@ietfa.amsl.com>; Wed, 15 Jun 2016 22:26:06 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2B2412D0FB for <pce@ietf.org>; Wed, 15 Jun 2016 22:26:05 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml703-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CQW90102; Thu, 16 Jun 2016 05:26:03 +0000 (GMT)
Received: from BLREML408-HUB.china.huawei.com (10.20.4.47) by lhreml703-cah.china.huawei.com (10.201.5.104) with Microsoft SMTP Server (TLS) id 14.3.235.1; Thu, 16 Jun 2016 06:26:02 +0100
Received: from BLREML501-MBB.china.huawei.com ([10.20.5.200]) by BLREML408-HUB.china.huawei.com ([10.20.4.47]) with mapi id 14.03.0235.001; Thu, 16 Jun 2016 10:55:48 +0530
From: Dhruv Dhody <dhruv.dhody@huawei.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 'Ramon Casellas' <ramon.casellas@cttc.es>, "pce@ietf.org" <pce@ietf.org>
Thread-Topic: [Pce] Experimental Codepoints allocation in PCEP registry
Thread-Index: AdHHj4XTYvk1JECTRtGWzA74BJvPuA==
Date: Thu, 16 Jun 2016 05:25:47 +0000
Message-ID: <23CE718903A838468A8B325B80962F9B8C860EEA@blreml501-mbb>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.244.252]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.5762386B.0102, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 8ded8743d88dc5d549456e267a750aa5
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/XQ1uYTHvyZewMKFKG6u1AN2XgB4>
Subject: Re: [Pce] Experimental Codepoints allocation in PCEP registry
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jun 2016 05:26:08 -0000

Hi Adrian,

> How would you all feel about 8? (My instinct is to push for 4, but I can
> pre-emptively compromise :-)

I can work with 8 :)

Regards,
Dhruv

> -----Original Message-----
> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
> Sent: 15 June 2016 23:52
> To: Dhruv Dhody <dhruv.dhody@huawei.com>; 'Ramon Casellas'
> <ramon.casellas@cttc.es>; pce@ietf.org
> Subject: RE: [Pce] Experimental Codepoint allocation in PCEP registry
> 
> To Ramon's point...
> 
> > We do need to reach a consensus on what range to set aside.
> 
> Yes, we do. Both to satisfy ourselves and to get past the current IESG (not
> the one that approved the MANET registry).
> 
> I think you captured the essence. There should be enough code points to run
> the parallel experiments that need to be run together, but not so many that
> experiments that don't need to be run at the same time can grab values and
> expect to keep them. Essentially, before running an experiment all
> participants should get together to agree what values to use, and then when
> the experiment is over they should consider the values to have no meaning
> (until the next and completely different experiment).
> 
> As far as I can see, 30 messages looks like a complete orgy of experimentation!
> Four times more active experimentation in one experimental network than in
> the whole of the standardised and soon-to-be standardised history of PCEP.
> 
> How would you all feel about 8? (My instinct is to push for 4, but I can
> pre-emptively compromise :-)
> 
> Adrian
> 
> > -----Original Message-----
> > From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Dhruv Dhody
> > Sent: 10 June 2016 11:03
> > To: Ramon Casellas; pce@ietf.org
> > Subject: Re: [Pce] Experimental Codepoint allocation in PCEP registry
> >
> > Hi Ramon,
> >
> > > -----Original Message-----
> > > From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Ramon Casellas
> > > Sent: 10 June 2016 14:42
> > > To: pce@ietf.org
> > > Subject: Re: [Pce] Experimental Codepoint allocation in PCEP
> > > registry
> > >
> > > Hi Dhruv, Jeff, all
> > >
> > > Indeed. Having been involved in PCE-related experimental and
> > > research activities I would welcome this and could be very helpful.
> > > It will not solve the issues but at least it defines the ranges.
> > >
> > > I can't provide much feedback, just curious about the rationale to
> > > allocate a given range e.g. 224-255 > 30 messages, etc.
> >
> > [Dhruv] You hit the jackpot.... we wanted to get the feedback of the
> > WG about this.
> >
> > IMHO we need to strike a right balance that there are enough
> > codepoints set aside for multiple parallel experimentations at a given
> > time, and not to give
> up a
> > big chunk out for experimentation that it hinders IANA allocation.
> >
> > We currently have 9 messages set by IANA, some 4 new messages in queue
> > to be sent to IANA, 13/255 ... so we do not have to worry about
> > running out any time soon :)
> >
> > BTW I could find one instance in MANET where a similar range is
> > allocated -
> > https://tools.ietf.org/html/rfc5444#section-6.2
> >
> > We do need to reach a consensus on what range to set aside.
> >
> > Regards,
> > Dhruv
> >
> > >
> > > Best regards
> > > Ramon
> > >
> > > On 10/06/2016 11:00, Jeff Tantsura wrote:
> > > > Hi Dhruv,
> > > >
> > > > Support, very much needed!
> > > >
> > > > Thanks,
> > > > Jeff
> > > >
> > > > On 6/9/16, 5:09 AM, "Pce on behalf of Dhruv Dhody"
> > > > <pce-bounces@ietf.org
> > > on behalf of dhruv.dhody@huawei.com> wrote:
> > > >
> > > >> Hi WG,
> > > >>
> > > >> In PCE IANA registry [http://www.iana.org/assignments/pcep] we do
> > > >> not
> > > have any codepoints for experimental usage. As we work on some new
> > experiments
> > > with PCEP (sometimes in open source platform), it would be wise to
> > > use experimental codepoints to avoid any conflict. For this purpose
> > > we have written a small draft to carve out some codepoints for
> > > experimental usage for PCEP messages, objects and TLVs.
> > > >>
> > > >> https://tools.ietf.org/html/draft-dhody-pce-pcep-exp-codepoints-0
> > > >> 0
> > > >>
> > > >> Please provide your feedback.
> > > >>
> > > >> Thanks,
> > > >> Dhruv & Daniel
> > > >>
> > > >> -----
> > > >>
> > > >> Name:           draft-dhody-pce-pcep-exp-codepoints
> > >
> > > _______________________________________________
> > > Pce mailing list
> > > Pce@ietf.org
> > > https://www.ietf.org/mailman/listinfo/pce
> >
> > _______________________________________________
> > Pce mailing list
> > Pce@ietf.org
> > https://www.ietf.org/mailman/listinfo/pce