IETF Logo Mail Archive

Re: [Idr] route-capability explained

"Samita Chakrabarti" <samitac@ipinfusion.com> Mon, 04 August 2008 20:48 UTC

Return-Path: <idr-bounces@ietf.org>
X-Original-To: idr-archive@megatron.ietf.org
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 469EE3A6C0B; Mon, 4 Aug 2008 13:48:09 -0700 (PDT)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0AB573A6A4C for <idr@core3.amsl.com>; Mon, 4 Aug 2008 13:48:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.592
X-Spam-Level:
X-Spam-Status: No, score=-0.592 tagged_above=-999 required=5 tests=[AWL=-0.407, BAYES_40=-0.185]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IvuAcLx81tpz for <idr@core3.amsl.com>; Mon, 4 Aug 2008 13:48:07 -0700 (PDT)
Received: from smtpauth02.prod.mesa1.secureserver.net (smtpauth02.prod.mesa1.secureserver.net [64.202.165.182]) by core3.amsl.com (Postfix) with SMTP id 08F2E3A6858 for <idr@ietf.org>; Mon, 4 Aug 2008 13:48:06 -0700 (PDT)
Received: (qmail 18481 invoked from network); 4 Aug 2008 20:48:32 -0000
Received: from unknown (65.223.109.250) by smtpauth02.prod.mesa1.secureserver.net (64.202.165.182) with ESMTP; 04 Aug 2008 20:48:32 -0000
From: Samita Chakrabarti <samitac@ipinfusion.com>
To: 'Paul Jakma' <paul@clubi.ie>
References: <000001c8f313$eaa095e0$2b168182@samitacD600> <alpine.LFD.1.10.0808011257360.4279@localhost.localdomain> <006101c8f65e$302551d0$97000a0a@samitacD600> <alpine.LFD.1.10.0808041931110.5059@localhost.localdomain> <006a01c8f669$7ce090b0$97000a0a@samitacD600> <alpine.LFD.1.10.0808042043330.5059@localhost.localdomain>
Date: Mon, 04 Aug 2008 13:48:28 -0700
Message-ID: <006b01c8f673$739cd8b0$97000a0a@samitacD600>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acj2ayhpS/HdKt+3QQmKtVR3TS/xBQAB98KQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <alpine.LFD.1.10.0808042043330.5059@localhost.localdomain>
Cc: 'Inter-Domain Routing List' <idr@ietf.org>, l3vpn@ietf.org
Subject: Re: [Idr] route-capability explained
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org


>> A deployment should be a RFC compliant. Draft-rekhter-as4octet is
>> an individual contribution now. When it becomes an RFC, the final
>> deployment should follow the RFC. But, folks can discuss more on
>> this and come up with a solution that works and scales.
>
>Ok.
>
>My vote is for constraining originators to encode 2:2 bytes of
>ASN:value (with the 2-byte extcom type code obviously) wherever
>possible, with 4:2 (4B code, obviously) if the AS value requires it.
>

[SC>] This is simple and it works for me too.

Any other comments from the wg?

Thanks,
-Samita


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

v2.23.0 | Report a Bug | By Email