IETF Logo Mail Archive

Re: [v6ops] draIn ft-ietf-v6ops-design-choices WGLC

Nick Hilliard <nick@foobar.org> Thu, 09 April 2015 15:43 UTC

Return-Path: <nick@foobar.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 992431B2DD9 for <v6ops@ietfa.amsl.com>; Thu, 9 Apr 2015 08:43:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nm0xxmQ99dXh for <v6ops@ietfa.amsl.com>; Thu, 9 Apr 2015 08:43:18 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 060251B2DD8 for <v6ops@ietf.org>; Thu, 9 Apr 2015 08:43:17 -0700 (PDT)
X-Envelope-To: <v6ops@ietf.org>
Received: from cupcake.foobar.org ([IPv6:2001:4d68:2002:100:0:0:0:110]) (authenticated bits=0) by mail.netability.ie (8.15.1/8.14.9) with ESMTPSA id t39FhFDT016489 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <v6ops@ietf.org>; Thu, 9 Apr 2015 16:43:16 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.netability.ie: Host [IPv6:2001:4d68:2002:100:0:0:0:110] claimed to be cupcake.foobar.org
Message-ID: <55269E13.9060803@foobar.org>
Date: Thu, 09 Apr 2015 16:43:15 +0100
From: Nick Hilliard <nick@foobar.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: v6ops@ietf.org
References: <7DF32A06-80FA-461A-A387-DE55F1DB79DB@magma.ca> <2004183372.2937208.1428540561672.JavaMail.yahoo@mail.yahoo.com> <4FC37E442D05A748896589E468752CAA0CDAFE85@PWN401EA160.ent.corp.bcbsm.com> <55269B8C.7060703@foobar.org>
In-Reply-To: <55269B8C.7060703@foobar.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/R7ZrsnP2d0dOYZQn5bUCuDRlMPo>
Subject: Re: [v6ops] draIn ft-ietf-v6ops-design-choices WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 15:43:19 -0000

On 09/04/2015 16:32, Nick Hilliard wrote:
> Large-scale provider networks would normally use a GUA as a next-hop for
> the bgp prefix and set it to be the address of the PE device which
> originated the prefix.

I should qualify this a bit better: large scale providers running native
ipv6 will do this.  Many large scale providers will run ipv6 on mpls/6pe,
where the bgp NH IP is the ipv4 identifier address of the PE.

Nick

v2.46.0 | Report a Bug | By Email | System Status