IETF Logo Mail Archive

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

Paul Kyzivat <pkyzivat@alum.mit.edu> Sat, 12 October 2013 00:03 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 4BD0A21F9B65 for <mmusic@ietfa.amsl.com>; Fri, 11 Oct 2013 17:03:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.256
X-Spam-Level:
X-Spam-Status: No, score=-0.256 tagged_above=-999 required=5 tests=[AWL=0.181, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.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 fIM0+cGn7EED for <mmusic@ietfa.amsl.com>; Fri, 11 Oct 2013 17:03:24 -0700 (PDT)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:243]) by ietfa.amsl.com (Postfix) with ESMTP id 5982C21F9B08 for <mmusic@ietf.org>; Fri, 11 Oct 2013 17:03:23 -0700 (PDT)
Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by qmta13.westchester.pa.mail.comcast.net with comcast id bzwH1m0011ap0As5D03Pic; Sat, 12 Oct 2013 00:03:23 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta22.westchester.pa.mail.comcast.net with comcast id c03P1m00E3ZTu2S3i03PAj; Sat, 12 Oct 2013 00:03:23 +0000
Message-ID: <525891C9.4050904@alum.mit.edu>
Date: Fri, 11 Oct 2013 20:03:21 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: mmusic@ietf.org
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> <5255C3A7.6000104@cisco.com> <5255D88E.1050600@alum.mit.edu> <949EF20990823C4C85C18D59AA11AD8B0B40E4@FR712WXCHMBA11.zeu.alcatel-lucent.com> <5257269D.6080600@alum.mit.edu> <949EF20990823C4C85C18D59AA11AD8B0B6174@FR712WXCHMBA11.zeu.alcatel-lucent.com> <52582C13.70906@alum.mit.edu> <52586602.7050802@cisco.com>
In-Reply-To: <52586602.7050802@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1381536203; bh=b86ceQVBpE5qBEfRsyBdmyLPpsXDIlr0ZdDeP3zB5wU=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=gH0khyKnwzRhN+lHyW4W41G3FVhk0f9I3wvoRfn4sEI6tVKeNLsiI184fR3TOguqd J/RC0HCSJx6ia8TajfryGvi0YQrB0XwG4uHoGTX6KokQzYe46lFXRjRdw+5XoJ0+nu HveYXEjeDuDB8p32QbTey80iPy00gZKebKuW3Ryz4A3AmdK7g56a6J/W+78NnFbO0q 6rrDxAUhv1IQjqv5XNTRgkR/ui5g52XBJmCNHoH7aaRHyOFadOpqLNCgDV0sL5MfYM AIkzmovWOrtls4fRraMheX2mzHPARqePFLy2pZjB5c59BiVRAe7qmL2Au88qd1oUCO pgH2dU0XiJ3zQ==
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: Sat, 12 Oct 2013 00:03:30 -0000

On 10/11/13 4:56 PM, Flemming Andreasen wrote:
>
> On 10/11/13 12:49 PM, Paul Kyzivat wrote:
>>
>> I must say that I am troubled that 4566 does not make the registration
>> of new network or address types mandatory. ("New network(address)
>> types ... *may* be registered with IANA") The current situation almost
>> tripped over this. If new ones aren't registered, then how is someone
>> who wants to define a new one to know if the chosen name is already
>> taken.
>>
> Fair point; want to start a new thread on this ?

Does this require a thread of its own?
I'm thinking this is just part of a more general task to clean up the 
IANA registries for SDP. (Probably as part of 4566bis.)

But I hesitate to kick of a discussion now that might be active.
I am swamped in another context right now.

	Thanks,
	Paul

v2.23.0 | Report a Bug | By Email