nanog mailing list archives
Re: [ppml] Fw: ":" - Re: Proposed Policy: 4-Byte AS Number Policy Proposal
From: Owen DeLong <owen () delong com>
Date: Thu, 15 Dec 2005 23:53:31 -0800
Actually, for actual implementation, there are subtle differences between AS 0x0002 ans AS 0x00000002. True, they are the same AS in 16 and 32 bit representation, and, for allocation policy, they are the same, but, in actual router guts, there are limited circumstances where you might actually care which one you are talking about. Owen --On December 15, 2005 1:45:20 PM -0500 Todd Vierling <tv () duh org> wrote:
On Wed, 14 Dec 2005, Robert Bonomi wrote:> That's an example of the lack of plain English in the > proposal. Why don't we just talk about AS numbers greater > than 65535 or AS numbers less than 65536? Because there is more to it than just that. :)No, there isn't. AS numbers are integers. It just so happens that there are now two representations of said integers with different domain bounds. Any other interpretation simply adds too much confusion. After all, "2 byte AS2" vs. "4 byte AS2" implies *more than* 4 bytes -- because you have to use metadata beyond the 4 bytes to represent which "type" of AS you have.
-- If this message was not signed with gpg key 0FE2AA3D, it's probably a forgery.
Attachment:
_bin
Description:
Current thread:
- Re: [ppml] Fw: ":" - Re: Proposed Policy: 4-Byte AS Number Policy Proposal Robert Bonomi (Dec 14)
- Re: [ppml] Fw: ":" - Re: Proposed Policy: 4-Byte AS Number Policy Proposal Michael . Dillon (Dec 14)
- Re: [ppml] Fw: ":" - Re: Proposed Policy: 4-Byte AS Number Policy Proposal Todd Vierling (Dec 15)
- Re: [ppml] Fw: ":" - Re: Proposed Policy: 4-Byte AS Number Policy Proposal Owen DeLong (Dec 15)
- Re: [ppml] Fw: ":" - Re: Proposed Policy: 4-Byte AS Number Policy Proposal Todd Vierling (Dec 16)
- Re: [ppml] Fw: ":" - Re: Proposed Policy: 4-Byte AS Number Policy Proposal Owen DeLong (Dec 15)