Re: [RAI] Conference Focus Indicating CCMP Support draft

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Thu, 11 April 2013 01:26 UTC

Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: rai@ietfa.amsl.com
Delivered-To: rai@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6844421F8A91 for <rai@ietfa.amsl.com>; Wed, 10 Apr 2013 18:26:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 DKelV8O3rGHR for <rai@ietfa.amsl.com>; Wed, 10 Apr 2013 18:26:46 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 8B64A21F8A7E for <rai@ietf.org>; Wed, 10 Apr 2013 18:26:46 -0700 (PDT)
Received: from us70tusmtp1.zam.alcatel-lucent.com (h135-5-2-63.lucent.com [135.5.2.63]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r3B1QgMj021768 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 10 Apr 2013 20:26:42 -0500 (CDT)
Received: from US70UWXCHHUB02.zam.alcatel-lucent.com (us70uwxchhub02.zam.alcatel-lucent.com [135.5.2.49]) by us70tusmtp1.zam.alcatel-lucent.com (GMO) with ESMTP id r3B1QerH007595 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 10 Apr 2013 21:26:41 -0400
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (135.239.2.74) by US70UWXCHHUB02.zam.alcatel-lucent.com (135.5.2.49) with Microsoft SMTP Server (TLS) id 14.2.247.3; Wed, 10 Apr 2013 21:26:40 -0400
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.201]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Thu, 11 Apr 2013 03:26:37 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com>, Robert Sparks <rjsparks@nostrum.com>
Thread-Topic: Conference Focus Indicating CCMP Support draft
Thread-Index: Ac41UqOwQn61izg0SJyesqCVCdwaeQAkIBsAAA26cIAABtgOsP//+foAgABAFUD///4KoA==
Date: Thu, 11 Apr 2013 01:26:36 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B0260CD@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <C563F76EA324474CA3722A35154AFDB3139FD6D9@AZ-US1EXMB01.global.avaya.com> <51651C5C.1020104@ericsson.com> <5165787D.8010501@nostrum.com> <C563F76EA324474CA3722A35154AFDB3139FDF7F@AZ-US1EXMB01.global.avaya.com> <5165A15E.20401@nostrum.com> <C563F76EA324474CA3722A35154AFDB3139FDFCB@AZ-US1EXMB01.global.avaya.com>
In-Reply-To: <C563F76EA324474CA3722A35154AFDB3139FDFCB@AZ-US1EXMB01.global.avaya.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Cc: "rai@ietf.org" <rai@ietf.org>
Subject: Re: [RAI] Conference Focus Indicating CCMP Support draft
X-BeenThere: rai@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Real-time Applications and Infrastructure \(RAI\)" <rai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rai>, <mailto:rai-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rai>
List-Post: <mailto:rai@ietf.org>
List-Help: <mailto:rai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rai>, <mailto:rai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Apr 2013 01:26:47 -0000

I prefer the approach to that defines the ABNF in a way that allows it to be extended with 

info-purpose-choices =/ "foo"

in a future specification or other document.

Keith

> -----Original Message-----
> From: rai-bounces@ietf.org [mailto:rai-bounces@ietf.org] On Behalf Of
> Shekh-Yusef, Rifaat (Rifaat)
> Sent: 10 April 2013 18:51
> To: Robert Sparks
> Cc: rai@ietf.org
> Subject: Re: [RAI] Conference Focus Indicating CCMP Support draft
> 
> Adding the RAI distribution to this discussion per Robert's request.
> 
> 
> Thanks Robert,
> 
> > That _redefines_ Call-Info even if it leaves the syntax the same.
> > The definition for the header would be in _this_ document, not in 3261
> > if you leave the ABNF like this.
> 
> I now understand your concern.
> I would like to go with the option of removing the ABNF and just define
> the new value.
> 
> 
> Do others see value with the second option:
> 
> > But if you do mess with the ABNF, make this change:
> >
> > info-param = ( "purpose" EQUAL ( info-purpose-choices) ) / generic-param
> > info-purpose-choices = "icon" / "info" / "card" / "ccmp " / token
> >
> > so that  the _next_ draft that comes along that wants to add a purpose
> > choice can simply say
> > info-purpose-choices =/ "foo"
> >
> > If you go down this path, you should also check with the community
> > whether we should
> > create an IANA registry for these choices. I don't think it's worth it,
> > but there have been
> > similar conversations where the rough consensus was to create one.
> 
> 
> Thanks,
>  Rifaat
> 
> 
> > -----Original Message-----
> > From: Robert Sparks [mailto:rjsparks@nostrum.com]
> > Sent: Wednesday, April 10, 2013 1:29 PM
> > To: Shekh-Yusef, Rifaat (Rifaat)
> > Cc: Gonzalo Camarillo; rlb@ipv.sx; Mary Barnes; Alan Johnston
> > Subject: Re: Conference Focus Indicating CCMP Support draft
> >
> > On 4/10/13 12:08 PM, Shekh-Yusef, Rifaat (Rifaat) wrote:
> > > Hi Robert,
> > >
> > > Thanks for your feedback.
> > >
> > >> The one thing that sticks out is the complete redefinition of the
> > >> Call-Info header syntax just to add a parameter
> > >> to info-param.
> > > The draft is not changing the syntax of the Call-Info header; the
> > absoluteURI will be an XCON-URI and we are defining a new "ccmp" token
> > to indicate that the URI supports ccmp.
> > > Where do you see that we are redefining the syntax?
> > The draft contains this:
> >
> >     The following is the updated ABNF for the Call-Info header:
> >
> >        Call-Info   =  "Call-Info" HCOLON info *(COMMA info)
> >        info        =  LAQUOT absoluteURI RAQUOT *( SEMI info-param)
> >        info-param  =  ( "purpose" EQUAL ( "icon" / "info"
> >                       / "card" / "ccmp" / token ) ) / generic-param
> >
> > That _redefines_ Call-Info even if it leaves the syntax the same.
> > The definition for the header would be in _this_ document, not in 3261
> > if you leave the ABNF like this.
> >
> > At the very least, don't restate Call-Info and info. Redefine only
> > info-param.
> >
> > You could just define the value and not mess with the ABNF. That is the
> > avenue I would recommend.
> >
> > But if you do mess with the ABNF, make this change:
> >
> > info-param = ( "purpose" EQUAL ( info-purpose-choices) ) / generic-param
> > info-purpose-choices = "icon" / "info" / "card" / "ccmp " / token
> >
> > so that  the _next_ draft that comes along that wants to add a purpose
> > choice can simply say
> > info-purpose-choices =/ "foo"
> >
> > If you go down this path, you should also check with the community
> > whether we should
> > create an IANA registry for these choices. I don't think it's worth it,
> > but there have been
> > similar conversations where the rough consensus was to create one.
> >
> > Also, it's unfortunate that this conversation isn't on a list. If we
> > continue, please add a list to the distribution.
> > I suggest rai@ietf.org.
> >
> > RjS
> >
> >
> >
> > >
> > > Regards,
> > >   Rifaat
> > >
> > >
> > >> -----Original Message-----
> > >> From: Robert Sparks [mailto:rjsparks@nostrum.com]
> > >> Sent: Wednesday, April 10, 2013 10:35 AM
> > >> To: Gonzalo Camarillo
> > >> Cc: Shekh-Yusef, Rifaat (Rifaat); rlb@ipv.sx; Mary Barnes; Alan
> > Johnston
> > >> Subject: Re: Conference Focus Indicating CCMP Support draft
> > >>
> > >> We had not yet started. The next step is for the authors to request
> > >> publication (when they believe it is ready),
> > >> and you or Richard can start fresh with an initial AD review.
> > >>
> > >> I skimmed the version of the draft linked to below - I still don't
> > >> expect controversy or much in the way of changes.
> > >> The one thing that sticks out is the complete redefinition of the
> > >> Call-Info header syntax just to add a parameter
> > >> to info-param. It would be much better to find a way to use the
> > >> Incremental Alternative (=/) production rule.
> > >> If that's not possible the way Call-Info is currently defined, we
> > should
> > >> redefine it _once_ to make it possible.
> > >> IIRC there are other things in flight that are touching Call-Info -
> > you
> > >> should make sure they're aligned.
> > >>
> > >> RjS
> > >>
> > >> On 4/10/13 3:01 AM, Gonzalo Camarillo wrote:
> > >>> Hi Robert,
> > >>>
> > >>> the authors of the draft below just sent us the email below. They
> > >>> mention you had agreed to AD sponsor it. What is the next step here
> > so
> > >>> that Richard or I can take this over?
> > >>>
> > >>> Thanks,
> > >>>
> > >>> Gonzalo
> > >>>
> > >>> On 09/04/2013 9:47 PM, Shekh-Yusef, Rifaat (Rifaat) wrote:
> > >>>> Gonzalo, Richard,
> > >>>>
> > >>>>
> > >>>>
> > >>>> Mary and I have been working on the following "Conference Focus
> > >>>> Indicating CCMP Support" draft, which Robert agreed to AD sponsor a
> > >>>> while back.
> > >>>>
> > >>>> https://datatracker.ietf.org/doc/draft-yusef-dispatch-ccmp-
> > >> indication/?include_text=1
> > >>>>
> > >>>>
> > >>>> The draft is simple and straightforward which was discussed on the
> > >>>> DISPATCH mailing list.
> > >>>>
> > >>>> Robert Sparks, Alan Johnston, Cullen Jennings, and Adam Roach all
> > >>>> reviewed it and provided feedback which was incorporated into the
> > >> latest
> > >>>> version of the draft.
> > >>>>
> > >>>> Alan Johnston is the document shepherd and he worked on the writeup
> > >> for
> > >>>> this draft.
> > >>>>
> > >>>>
> > >>>>
> > >>>> Now that Robert is no longer an AD, can one of you please sponsor
> > >> this
> > >>>> draft instead?
> > >>>>
> > >>>>
> > >>>>
> > >>>> Thanks,
> > >>>>
> > >>>> Rifaat
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> 
> _______________________________________________
> RAI mailing list
> RAI@ietf.org
> https://www.ietf.org/mailman/listinfo/rai