RE: [MBONED] addrarch: resurrect IPv4 unicast-prefix-based?

Dave Thaler <dthaler@windows.microsoft.com> Sat, 20 January 2007 01:36 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H859L-0000IZ-Tq; Fri, 19 Jan 2007 20:36:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H859K-0000IT-F3 for mboned@ietf.org; Fri, 19 Jan 2007 20:36:06 -0500
Received: from smtp.microsoft.com ([131.107.115.215]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H859J-0006ZZ-3R for mboned@ietf.org; Fri, 19 Jan 2007 20:36:06 -0500
Received: from tk1-exhub-c103.redmond.corp.microsoft.com (157.56.116.114) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.0.685.24; Fri, 19 Jan 2007 17:36:00 -0800
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com (157.54.69.169) by tk1-exhub-c103.redmond.corp.microsoft.com (157.56.116.114) with Microsoft SMTP Server id 8.0.685.24; Fri, 19 Jan 2007 17:36:00 -0800
Received: from WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com ([157.54.62.25]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.2825); Fri, 19 Jan 2007 17:35:58 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MBONED] addrarch: resurrect IPv4 unicast-prefix-based?
Date: Fri, 19 Jan 2007 17:35:09 -0800
Message-ID: <271CF87FD652F34DBF877CB0CB5D16FC0406349C@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <Pine.LNX.4.64.0701190954050.28931@netcore.fi>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
thread-topic: [MBONED] addrarch: resurrect IPv4 unicast-prefix-based?
thread-index: Acc7oHhO5iGZtu8MSwGJJwqGr8GJqAAkmkdw
References: <Pine.LNX.4.64.0612201329120.22781@netcore.fi><20061220153322.GA2160@1-4-5.net><F9078A40-6E1C-4179-8167-C165B1F90011@multicasttech.com><20061220155329.GA4441@1-4-5.net> <Pine.LNX.4.64.0701190954050.28931@netcore.fi>
From: Dave Thaler <dthaler@windows.microsoft.com>
To: Pekka Savola <pekkas@netcore.fi>
X-OriginalArrivalTime: 20 Jan 2007 01:35:58.0086 (UTC) FILETIME=[559F7260:01C73C33]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: mboned@ietf.org
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
Errors-To: mboned-bounces@ietf.org

I let the document expire due to lack of strong interest.
If there is interest, I am willing to continue as editor.

I am not aware of current open issues or unresolved comments, but 
there are some boilerplate things that would need to be fixed up to
conform to the latest I-D guidelines (the copyright notice for instance)
before resubmitting.

-Dave

> -----Original Message-----
> From: Pekka Savola [mailto:pekkas@netcore.fi]
> Sent: Friday, January 19, 2007 12:04 AM
> To: mboned@ietf.org
> Subject: [MBONED] addrarch: resurrect IPv4 unicast-prefix-based?
> 
> Summarizing this part of the discussion,
> 
> Given that with 4-byte ASNs, GLOP is no longer applicable (the first
> 4-byte *ONLY* ASN could take a few years to appear, some 4-byte ASNs
> have already been tested though), there was some discussion of IPv4
> unicast-prefix-based mechanism
> [draft-ietf-mboned-ipv4-uni-based-mcast] which expired in 2004 due to
> lack of no clear benefit (compared to GLOP, for instance).
> 
> Lenny argued for resurrecting the draft so that IANA would not need to
> be consulted so often to get addresses.  Marshall noted that in many
> (current) cases where a requestor wants addresses and GLOP doesn't
> satisfy, they don't have enough v4 addresses either.  Toerless seemed
> supportive of resurrecting ipv4-uni-based-mcast.  John Kristoff also
> supported this approach.
> 
> As there didn't seem to be objection, and there is a new user group
> (upcoming 4byte ASN holders) that didn't exist when the draft expired,
> this might be sufficient inclination that there is interest in it.
> I'll note that doing so will require a /8 of address space.
> 
> What do the chairs think of this?  Is this something that can be taken
> up?  Who'd be the editor?  What kind of schedule would we have for
> pushing this through (should ADDRARCH wait for this or not)?
> 
> --
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
> 
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www1.ietf.org/mailman/listinfo/mboned


_______________________________________________
MBONED mailing list
MBONED@ietf.org
https://www1.ietf.org/mailman/listinfo/mboned