RE: [PWE3] RE: Appropriate addressing
"Chris Metz \(chmetz\)" <chmetz@cisco.com> Wed, 10 August 2005 16:55 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E2trc-0003ZZ-Fq; Wed, 10 Aug 2005 12:55:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E2tra-0003ZU-3K for pwe3@megatron.ietf.org; Wed, 10 Aug 2005 12:55:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10803 for <pwe3@ietf.org>; Wed, 10 Aug 2005 12:55:31 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E2uPh-0004NF-3r for pwe3@ietf.org; Wed, 10 Aug 2005 13:30:51 -0400
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-1.cisco.com with ESMTP; 10 Aug 2005 09:55:22 -0700
X-IronPort-AV: i="3.96,97,1122879600"; d="scan'208"; a="654009329:sNHT35324040"
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j7AGt10X002836; Wed, 10 Aug 2005 09:55:19 -0700 (PDT)
Received: from xmb-rtp-202.amer.cisco.com ([64.102.31.52]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 10 Aug 2005 12:55:17 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: RE: [PWE3] RE: Appropriate addressing
Date: Wed, 10 Aug 2005 12:55:16 -0400
Message-ID: <EAE1CBBD071180449FC50C37CFC78394687FD5@xmb-rtp-202.amer.cisco.com>
Thread-Topic: [PWE3] RE: Appropriate addressing
Thread-Index: AcWdTRIoGnsSL0O/SeeBwycN8aw/2wAJ0v/wABWPkzA=
From: "Chris Metz (chmetz)" <chmetz@cisco.com>
To: richard.spencer@bt.com, "Scott Brim (sbrim)" <sbrim@cisco.com>, pwe3@ietf.org
X-OriginalArrivalTime: 10 Aug 2005 16:55:17.0975 (UTC) FILETIME=[495E8E70:01C59DCC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: quoted-printable
Cc:
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
All- It is precisely for the reasons spelled out by Scott, Luca, Neil, et al. that: http://www.ietf.org/internet-drafts/draft-metz-aii-aggregate-00.txt was cooked up. Clearly we need a PW end-point "name" or "address space" with the following properties: - aggregatable - flexible enough to accommodate (if desired) familiar/known address structures (understanding of course that they are completely separate from the whatever network layer addressing scheme is in place). - option for global uniqueness The actual field formats will change a little with some different names but essentially can accommodate the canonical structure described by Richard below. Chris <snip> >for example a PW endpoint > address is of the format [AS#]+[PE loopback]+[PW ID], <snip> _______________________________________________ pwe3 mailing list pwe3@ietf.org https://www1.ietf.org/mailman/listinfo/pwe3
- [PWE3] RE: Appropriate addressing richard.spencer
- RE: [PWE3] RE: Appropriate addressing Don Fedyk
- RE: [PWE3] RE: Appropriate addressing Chris Metz (chmetz)
- RE: [PWE3] RE: Appropriate addressing neil.2.harrison