IETF Logo Mail Archive

Re: [RAI] Conference Focus Indicating CCMP Support draft

worley@ariadne.com (Dale R. Worley) Thu, 11 April 2013 23:08 UTC

Return-Path: <worley@shell01.TheWorld.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 8AE5421F899E for <rai@ietfa.amsl.com>; Thu, 11 Apr 2013 16:08:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.377
X-Spam-Level:
X-Spam-Status: No, score=-2.377 tagged_above=-999 required=5 tests=[AWL=0.603, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
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 XeEdEQVURZH6 for <rai@ietfa.amsl.com>; Thu, 11 Apr 2013 16:08:04 -0700 (PDT)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id C436D21F89D3 for <rai@ietf.org>; Thu, 11 Apr 2013 16:08:02 -0700 (PDT)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r3BN7XfU007340; Thu, 11 Apr 2013 19:07:35 -0400
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id r3BN7WDU2404098; Thu, 11 Apr 2013 19:07:33 -0400 (EDT)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r3BN7Wj52395441; Thu, 11 Apr 2013 19:07:32 -0400 (EDT)
Date: Thu, 11 Apr 2013 19:07:32 -0400 (EDT)
Message-Id: <201304112307.r3BN7Wj52395441@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: "Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com>
In-reply-to: <C563F76EA324474CA3722A35154AFDB3139FDFCB@AZ-US1EXMB01.global.avaya.com> (rifatyu@avaya.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>
Cc: 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 23:08:07 -0000

> From: "Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com>
> 
> 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"

In abstract, I think I prefer the "second option".  But it would take
more bureaucratic work to implement it.

However, draft-yusef-dispatch-ccmp-indication-02, proposes creating a
registry for the predefined values of the purpose parameter of
Call-Info.  I'm not sure it's needed, as there are currently only 4
RFCs/drafts that are relevant.  But if a new registry is defined, the
document that defines it must initialize the registry with all of the
currently defined values, and the current section 4.2 only lists the
value "ccmp".  And it would need to update the row for "Call-Info" in 
"Header Field Parameters and Parameter Values" to reference the new
registry, rather than the collection of RFCs.

Dale

v2.8.7 | Report a Bug | By Email