Re: [Idr] Re: draft-ietf-idr-as-pathlimit-03.txt

Paul Jakma <paul@clubi.ie> Mon, 30 July 2007 13:24 UTC

Return-path: <idr-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IFVEy-0000o1-Qh; Mon, 30 Jul 2007 09:24:52 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IFVEw-0000no-US for idr@ietf.org; Mon, 30 Jul 2007 09:24:50 -0400
Received: from hibernia.jakma.org ([212.17.55.49]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFVEw-00053l-9N for idr@ietf.org; Mon, 30 Jul 2007 09:24:50 -0400
Received: from hibernia.jakma.org (IDENT:U2FsdGVkX1/KZK0Flj73M5fn1YUqkMJ7m6fMhf5mZBI@hibernia.jakma.org [212.17.55.49] (may be forged)) (authenticated bits=0) by hibernia.jakma.org (8.14.1/8.14.1) with ESMTP id l6UDOJqG002007 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 Jul 2007 14:24:24 +0100
Date: Mon, 30 Jul 2007 14:24:19 +0100
From: Paul Jakma <paul@clubi.ie>
X-X-Sender: paul@hibernia.jakma.org
To: Tony Li <tli@cisco.com>
Subject: Re: [Idr] Re: draft-ietf-idr-as-pathlimit-03.txt
In-Reply-To: <FF8A0162-D692-41F1-85A4-49CEE0602FD2@cisco.com>
Message-ID: <Pine.LNX.4.64.0707301417080.418@hibernia.jakma.org>
References: <77ead0ec0706071402p48baaa24yef6f17cb1d2e8cd6@mail.gmail.com> <FF8A0162-D692-41F1-85A4-49CEE0602FD2@cisco.com>
Mail-Copies-To: paul@jakma.org
X-NSA: al aqsar fluffy jihad cute musharef kittens jet-A1 ear avgas wax ammonium bad qran dog inshallah allah al-akbar martyr iraq hammas hisballah rabin ayatollah korea revolt pelvix mustard gas x-ray british airways washington peroxide cool
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (hibernia.jakma.org [212.17.55.49]); Mon, 30 Jul 2007 14:24:24 +0100 (IST)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: Inter-Domain Routing List <idr@ietf.org>
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Errors-To: idr-bounces@ietf.org

Hi Tony,

A query on the following language in the draft:

    If the AS_PATHLIMIT attribute is attached to a prefix by a private
    AS, then when the prefix is advertised outside of the parent AS, the
    AS number contained in the AS_PATHLIMIT attribute should be replaced
    by the AS number of the parent AS.

Could it be made more explicit here as to which speaker is 
responsible here?

E.g. is it the responsibility of /all/ pathlimit capable speakers to 
update a private-AS in a pathlimit with a public one (the attribute 
may transit one or more non-pathlimit capable ASes while containing a 
private AS)?

Should a speaker with a private AS, implementing this attribute, be 
pro-active and, when sending an UPDATE to a non-private-AS, set the 
pathlimit AS in such an UPDATE to the peer's ASN?

regards,
-- 
Paul Jakma	paul@clubi.ie	paul@jakma.org	Key ID: 64A2FF6A
Fortune:
No man would listen to you talk if he didn't know it was his turn next.
 		-- E.W. Howe

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr