Re: [MMUSIC] Updating SDP parameter registry with RFC3108 values

Flemming Andreasen <fandreas@cisco.com> Wed, 09 October 2013 20:59 UTC

Return-Path: <fandreas@cisco.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E40C121E81AF for <mmusic@ietfa.amsl.com>; Wed, 9 Oct 2013 13:59:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 6IwwfSpKjY0v for <mmusic@ietfa.amsl.com>; Wed, 9 Oct 2013 13:59:45 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 4F41C21F9B86 for <mmusic@ietf.org>; Wed, 9 Oct 2013 13:59:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4403; q=dns/txt; s=iport; t=1381352385; x=1382561985; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=tgcbIVAS9v1S8mt/U4ifcw43+/9x/5y7Gw8wPcAvf6I=; b=JGJwz3/oFUk3ol5woAjcVkMVN2XcSNDqVVLrHV/DQJD75z8BXwMr9fI/ NJ8xdNpwmoC2x8FjT5oKO6v/c07fxh1et0XZJDyHCxEr+weAn4h1Nz1b+ JN1xuIkYTsOVjfuHUJxZuD/sSku42I4WpZTZwQsMtnREOM/kCsiRx6nay E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArcMALPCVVKtJV2Y/2dsb2JhbABaDoJ5OK05A5QDSoEgFnSCJQEBAQMBAQEBNTMDCgEFCwsOCgkWDwkDAgECARUwBg0BBQIBAQWHdwYMuQWODIE5B4QjA5gDkgGCZVsggTU
X-IronPort-AV: E=Sophos;i="4.90,1066,1371081600"; d="scan'208";a="270205784"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-5.cisco.com with ESMTP; 09 Oct 2013 20:59:21 +0000
Received: from bxb-fandreas-8811.cisco.com (bxb-fandreas-8811.cisco.com [10.98.149.194]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r99KxKDf017414; Wed, 9 Oct 2013 20:59:20 GMT
Message-ID: <5255C3A7.6000104@cisco.com>
Date: Wed, 09 Oct 2013 16:59:19 -0400
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
References: <20130701185623.25213.31890.idtracker@ietfa.amsl.com> <523AEC68.5050005@nteczone.com> <5252109C.7020609@cisco.com> <52522A69.4020907@nteczone.com> <5252F30F.5000007@alum.mit.edu> <525339B5.3010300@nteczone.com> <52558227.3020300@alum.mit.edu>
In-Reply-To: <52558227.3020300@alum.mit.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] Updating SDP parameter registry with RFC3108 values
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Oct 2013 20:59:50 -0000

On 10/9/13 12:19 PM, Paul Kyzivat wrote:
> On 10/7/13 6:46 PM, Christian Groves wrote:
>> Hello Paul,
>>
>> Is a process needed to create an errata? Wouldn't the fact that they
>> appear in standards track RFCs be enough to include them in the SDP
>> registry based on the SDP directorates (i.e. expert review)
>> recommendation? I agree its not ideal that these older RFCs didn't
>> include an IANA considerations section but I think that rather than
>> spending lots of cycles on this that the SDP directorate could just
>> request IANA to register them to avoid any future overlap issues.
>
> Unfortunately there are rules. The rules for a particular IANA 
> registry are defined when the registry is created. If you check in the 
> registry, it points to RFC4566. Section 8.2.4 of RFC4566 says that 
> additions to this registry must follow the "Specification Required" 
> policy defined in RFC2434. And the specification must include a 
> particular set of information. (That would typically be in an IANA 
> considerations section.)
>
> At the moment all we have is RFC3108, and it doesn't have an IANA 
> considerations section at all. It certainly doesn't give the info 
> needed for an addition to that registry.
>
> IIUC, an errata to 3108 wouldn't, on its own, be sufficient either. I 
> think we will need a new RFC that does it. This should probably be an 
> update to 3108. An errata is perhaps a formal way to trigger that.
>
Having previously communicated with one of the RFC 3108 authors on this, 
I would ask for leniency here, not least considering that RFC 3108 
predates RFC 4566. In other words, I'd argue that we should simply add 
the missing registrations.

Thanks

-- Flemming



>     Thanks,
>     Paul
>
>> Regards, Christian
>>
>> On 8/10/2013 4:44 AM, Paul Kyzivat wrote:
>>> On 10/6/13 11:28 PM, Christian Groves wrote:
>>>> Hello Flemming,
>>>>
>>>> Thanks for pointing out that thread. If Paul as one of the SDP
>>>> directorate is OK with it then I don't have any issue with the -cs
>>>> draft.
>>>>
>>>> I think though that the addresstype and nettype from RFC3108 still 
>>>> needs
>>>> to be picked up by the IANA registry.
>>>
>>> I agree. I'm not sure what the best way to accomplish that is.
>>> Perhaps an errata to 3108, pointing out that it fails to register its
>>> new nettype and addrtypes with IANA would start the process. Or is
>>> there a better way?
>>>
>>>     Thanks,
>>>     Paul
>>>
>>>> Regards, Christian
>>>>
>>>> On 7/10/2013 12:38 PM, Flemming Andreasen wrote:
>>>>> Hi Christian
>>>>>
>>>>> We had a thread on this particular issue about a year ago. See
>>>>>
>>>>> http://www.ietf.org/mail-archive/web/mmusic/current/msg09599.html
>>>>>
>>>>> and the conclusion in
>>>>>
>>>>> http://www.ietf.org/mail-archive/web/mmusic/current/msg09621.html
>>>>>
>>>>> I hope this addresses your concern as it relates to -cs draft.
>>>>>
>>>>> Thanks
>>>>>
>>>>> -- Flemming
>>>>>
>>>>>
>>>>> On 9/19/13 8:22 AM, Christian Groves wrote:
>>>>>> FYI, I was looking at the IANA registry for SDP parameters (
>>>>>> http://www.iana.org/assignments/sdp-parameters/sdp-parameters.xhtml)
>>>>>> and noticed that there was a registration for addrtype E164 
>>>>>> linked to
>>>>>> this CS draft.
>>>>>>
>>>>>> There's a problem that there's already an addrtype E164 in RFC3108.
>>>>>> This earlier usage of E164 should have been registered with IANA but
>>>>>> seems to have been missed. To complicate things the format of the
>>>>>> RFC3108 E164 addrtype is different to the one in the CS draft.
>>>>>>
>>>>>> I've already raised this with IANA but I thought it would be worth
>>>>>> mentioning in MMUSIC.
>>>>>>
>>>>>> Christian
>>>>
>>>> _______________________________________________
>>>> mmusic mailing list
>>>> mmusic@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>>
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
> .
>