RE: [MBONED] addrarch: resurrect IPv4 unicast-prefix-based?
Pekka Savola <pekkas@netcore.fi> Tue, 30 January 2007 12:45 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBsMF-00032U-SY; Tue, 30 Jan 2007 07:45:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBsMD-00031K-Ik for mboned@ietf.org; Tue, 30 Jan 2007 07:45:05 -0500
Received: from eunet-gw.ipv6.netcore.fi ([2001:670:86:3001::1] helo=netcore.fi) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBsMC-0001q3-VF for mboned@ietf.org; Tue, 30 Jan 2007 07:45:05 -0500
Received: from localhost (pekkas@localhost) by netcore.fi (8.12.11.20060614/8.12.11) with ESMTP id l0UCintL017356; Tue, 30 Jan 2007 14:44:50 +0200
Date: Tue, 30 Jan 2007 14:44:49 +0200
From: Pekka Savola <pekkas@netcore.fi>
To: Dave Thaler <dthaler@windows.microsoft.com>
Subject: RE: [MBONED] addrarch: resurrect IPv4 unicast-prefix-based?
In-Reply-To: <271CF87FD652F34DBF877CB0CB5D16FC0406349C@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
Message-ID: <Pine.LNX.4.64.0701301444080.17345@netcore.fi>
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> <271CF87FD652F34DBF877CB0CB5D16FC0406349C@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Virus-Scanned: ClamAV 0.88.7/2501/Mon Jan 29 21:34:50 2007 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL, BAYES_00, NO_RELAYS autolearn=ham version=3.1.7
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on otso.netcore.fi
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
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
On Fri, 19 Jan 2007, Dave Thaler wrote: > 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. I'd certainly support this move, though if we go down this path, I'd hope we could get this published quickly. >> -----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 > > -- 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] addrarch: IANA allocations and assignmen… Pekka Savola
- Re: [MBONED] addrarch: IANA allocations and assig… Marshall Eubanks
- Re: [MBONED] addrarch: IANA allocations and assig… David Meyer
- Re: [MBONED] addrarch: IANA allocations and assig… Marshall Eubanks
- Re: [MBONED] addrarch: IANA allocations and assig… David Meyer
- Re: [MBONED] addrarch: IANA allocations and assig… Marshall Eubanks
- Re: [MBONED] addrarch: IANA allocations and assig… Toerless Eckert
- Re: [MBONED] addrarch: IANA allocations and assig… David Meyer
- Re: [MBONED] addrarch: IANA allocations and assig… Toerless Eckert
- Re: [MBONED] addrarch: IANA allocations and assig… David Meyer
- [MBONED] addrarch: resurrect IPv4 unicast-prefix-… Pekka Savola
- RE: [MBONED] addrarch: resurrect IPv4 unicast-pre… Dave Thaler
- RE: [MBONED] addrarch: resurrect IPv4 unicast-pre… Pekka Savola