IETF Logo Mail Archive

Re: [RAI] Conference Focus Indicating CCMP Support draft

"Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com> Sun, 14 April 2013 13:51 UTC

Return-Path: <rifatyu@avaya.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 C53E721F90C1 for <rai@ietfa.amsl.com>; Sun, 14 Apr 2013 06:51:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.432
X-Spam-Level:
X-Spam-Status: No, score=-3.432 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 JBdteEJKUq5F for <rai@ietfa.amsl.com>; Sun, 14 Apr 2013 06:51:48 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 2FB5D21F90B1 for <rai@ietf.org>; Sun, 14 Apr 2013 06:51:48 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAAH/ZlHGmAcF/2dsb2JhbABQgmUhNsFIgQcWdIIfAQEBAQMBAQEPKC4GCwwEAgEIDQQEAQELFAkHJwsUCQgCBA4FCBqHcgELoDydDBeNVIERJgsHBoJaYQOYI4UGimiDC4FzNQ
X-IronPort-AV: E=Sophos;i="4.87,456,1363147200"; d="scan'208";a="6899793"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 14 Apr 2013 09:51:47 -0400
Received: from unknown (HELO AZ-US1EXHC01.global.avaya.com) ([135.11.85.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 14 Apr 2013 09:48:45 -0400
Received: from AZ-US1EXMB01.global.avaya.com ([fe80::54fa:ed52:888e:7ca8]) by AZ-US1EXHC01.global.avaya.com ([135.11.85.12]) with mapi id 14.02.0328.009; Sun, 14 Apr 2013 09:51:46 -0400
From: "Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com>
To: "rai@ietf.org" <rai@ietf.org>
Thread-Topic: [RAI] Conference Focus Indicating CCMP Support draft
Thread-Index: Ac41UqOwQn61izg0SJyesqCVCdwaeQAkIBsAAA26cIAABtgOsP//+foAgABAFUCAAW3/Ev//GIzA//r+MPA=
Date: Sun, 14 Apr 2013 13:51:45 +0000
Message-ID: <C563F76EA324474CA3722A35154AFDB3139FF508@AZ-US1EXMB01.global.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> <201304112307.r3BN7Wj52395441@shell01.TheWorld.com> <C563F76EA324474CA3722A35154AFDB3139FEABA@AZ-US1EXMB01.global.avaya.com>
In-Reply-To: <C563F76EA324474CA3722A35154AFDB3139FEABA@AZ-US1EXMB01.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.11.85.47]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Sun, 14 Apr 2013 13:51:48 -0000

I have submitted a new version that removed the ABNF and changed the IANA section to address both the Call-Info and the URI registration.
http://tools.ietf.org/html/draft-yusef-dispatch-ccmp-indication-03

Please, take a look and let me know if you have any comments.

Thanks,
 Rifaat



> -----Original Message-----
> From: rai-bounces@ietf.org [mailto:rai-bounces@ietf.org] On Behalf Of
> Shekh-Yusef, Rifaat (Rifaat)
> Sent: Friday, April 12, 2013 9:01 AM
> To: Dale R. Worley
> Cc: rai@ietf.org
> Subject: Re: [RAI] Conference Focus Indicating CCMP Support draft
> 
> Hi Dale,
> 
> As Paul suggested in a previous email, I will follow what you did with
> your draft-ietf-bliss-call-completion.
> 
> Regards,
>  Rifaat
> 
> 
> > -----Original Message-----
> > From: Dale R. Worley [mailto:worley@ariadne.com]
> > Sent: Thursday, April 11, 2013 7:08 PM
> > To: Shekh-Yusef, Rifaat (Rifaat)
> > Cc: rjsparks@nostrum.com; rai@ietf.org
> > Subject: Re: [RAI] Conference Focus Indicating CCMP Support draft
> >
> > > 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
> _______________________________________________
> RAI mailing list
> RAI@ietf.org
> https://www.ietf.org/mailman/listinfo/rai

v2.23.0 | Report a Bug | By Email