[MMUSIC] RFC4566bis: what is the origin of change to IP6-address ???
Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 21 February 2019 00:08 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 51FB21274D0 for <mmusic@ietfa.amsl.com>; Wed, 20 Feb 2019 16:08:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id srreh-DdHrGZ for <mmusic@ietfa.amsl.com>; Wed, 20 Feb 2019 16:08:03 -0800 (PST)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82A28124BAA for <mmusic@ietf.org>; Wed, 20 Feb 2019 16:08:03 -0800 (PST)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x1L07mL3027655 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 20 Feb 2019 19:07:48 -0500
To: IETF MMUSIC WG <mmusic@ietf.org>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Cc: Mark Handley <M.Handley@cs.ucl.ac.uk>, 'Colin Perkins' <csp@csperkins.org>
Message-ID: <7fc571de-eadd-6929-d227-1453500c97bc@alum.mit.edu>
Date: Wed, 20 Feb 2019 19:07:47 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/gDaUeWQwWQ8qWhJqTxs3Z7YkV9U>
Subject: [MMUSIC] RFC4566bis: what is the origin of change to IP6-address ???
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 21 Feb 2019 00:08:05 -0000
In trying to clean up 4566bis I'm making a list of changes. A big one is the syntax of IP6-address. This is an entirely new definition. The old one had a reference to where it came from. The new one doesn't. I'm looking for the source of this, and why the change was made. The change appeared in -00 of 4566bis from 6-dec-2007. I haven't been able to figure out who submitted it. I found the announcement of this version in my own archives, but I found no other emails discussing it. Does anybody know: - the source for the IP6-address def? - who submitted the -00 version that made the change? Thanks, Paul
- [MMUSIC] RFC4566bis: what is the origin of change… Paul Kyzivat
- Re: [MMUSIC] RFC4566bis: what is the origin of ch… Colin Perkins
- Re: [MMUSIC] RFC4566bis: what is the origin of ch… Paul Kyzivat