Re: [Pce] Experimental Codepoint allocation in PCEP registry

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 15 June 2016 18:22 UTC

Return-Path: <adrian@olddog.co.uk>
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 AA3CE12B00A for <pce@ietfa.amsl.com>; Wed, 15 Jun 2016 11:22:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 4FbHSuzJTxLO for <pce@ietfa.amsl.com>; Wed, 15 Jun 2016 11:22:25 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AADF312D87D for <pce@ietf.org>; Wed, 15 Jun 2016 11:22:24 -0700 (PDT)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id u5FIMAxU023356; Wed, 15 Jun 2016 19:22:10 +0100
Received: from 950129200 (jplon-nat11.juniper.net [193.110.55.11]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id u5FIM74B023259 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 15 Jun 2016 19:22:09 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Dhruv Dhody' <dhruv.dhody@huawei.com>, 'Ramon Casellas' <ramon.casellas@cttc.es>, pce@ietf.org
References: <B1C930BE-326C-4DEC-A99C-01E6E0AD6C9C@gmail.com> <e9bba5a5-39b8-0103-edec-468b0ae7cd43@cttc.es> <23CE718903A838468A8B325B80962F9B8C819FB8@blreml501-mbx.china.huawei.com>
In-Reply-To: <23CE718903A838468A8B325B80962F9B8C819FB8@blreml501-mbx.china.huawei.com>
Date: Wed, 15 Jun 2016 19:22:05 +0100
Message-ID: <06f701d1c732$d359e070$7a0da150$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFjV7KopiYe+1BTUWLmmUo4dKmEMwJMa5g1Aac68uKgqBdycA==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.0.0.1202-22394.001
X-TM-AS-Result: No--24.195-10.0-31-10
X-imss-scan-details: No--24.195-10.0-31-10
X-TMASE-MatchedRID: gzVbiXtWD9vMy6K24fisqwPZZctd3P4BC/ExpXrHizyFLhVbWK8lx+Kn O+7eKYO58rDjqCD40fqG8tCUP4olE/UAEGUwHGlkfuyIS1Zjfrvys+HfIjrxyVvym/gvSH4iHOW W/Rp/isqfqcLD9bAPeYk1dImXpGTOR0d8YY6nEwXFlCgYxEaGE7OA0SKY3oCFLraGNlLRahjXnZ riPbsnGOmyFtI3fKXDzcRGA8aCRBoTY/HRCFabdLFPpfdetAtTOkDbNlgmO/XRyxuwHbF4CTFc3 2/RaBHN1bd6dtUtuuelW02WOAdEzA0zx+NDDxZ5BEfU2vugRF3DHSNFHFxB89w+R3dF+Lo0U9a6 zfLFA1aB201lqhaLgH3J0gEt3fM9RF8J0whn5t1CvapcIkxJXxkqnRJng/51DZjzHLL3eRZw8Qs vt3EaIAGiuhjxi3LNcRHmseYbxarau9iF5mAFe6m4PbloS2C3dZPoD9V2prSbKItl61J/ycnjLT A/UDoAHwAqApZ40aFix43hpI4fV90H8LFZNFG7JQhrLH5KSJ0=
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/OJVH--GpxchVQ3yZ9E7oOfI_mEY>
Subject: Re: [Pce] Experimental Codepoint allocation in PCEP registry
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Wed, 15 Jun 2016 18:22:26 -0000

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-00
> > >>
> > >> 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