IETF Logo Mail Archive

Re: Detail in draft-ietf-6man-segment-routing-header-06

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 04 April 2017 20:35 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C9D012950E for <ipv6@ietfa.amsl.com>; Tue, 4 Apr 2017 13:35:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 EUfD-X4qJeOP for <ipv6@ietfa.amsl.com>; Tue, 4 Apr 2017 13:35:08 -0700 (PDT)
Received: from mail-io0-x241.google.com (mail-io0-x241.google.com [IPv6:2607:f8b0:4001:c06::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A5C7126E3A for <ipv6@ietf.org>; Tue, 4 Apr 2017 13:35:08 -0700 (PDT)
Received: by mail-io0-x241.google.com with SMTP id f103so16135397ioi.2 for <ipv6@ietf.org>; Tue, 04 Apr 2017 13:35:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=IuaM7aFpv+PV5F9xjKZMDWBy4/bs+4kHbbJYD/zL2Ik=; b=F2s2zVqFEsLuYaKJkOZidfJJKaq1SqMyE/0U9Z6IxUlQjbPMHIIx8QYVhK8XKKFdXi ZQ15myVbsp2+02jLv5my5pNtf47lgrrD4JvBWoTQrOM3XuntHENvHWObfMVm0zIWIhY5 Vkm6KjLRRbiIUeiAnXVet27bvqN7e6mIBWYk2ATy5NI1+rSdDkbKK3rzNXm/EXIu15F/ m6lrNhB2wolYiG8LImT9aiAb71143Nv0hYpWswGErFeARSsdW+ELVLTiQgkuJcVzTDaP PiYG6BmK+IQBWBHVj4rXTmviJOV2enIVEATLklKVz5lIjU56dBJMwpp1pBj1T9M5/U55 HfwQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=IuaM7aFpv+PV5F9xjKZMDWBy4/bs+4kHbbJYD/zL2Ik=; b=Miq4UiuB5CYRqON20eeFh7Hl9fB43xl1IbL7df/+Ku0rt0mATL27wbcoXKZW/MGIWL MCMAir3zu2gf1PE6S/bUdgXX66+8elih5ijiPPtGfQthYW3LalK3fKFPMPit1LDAmL/m SJzYsGFrDi/iCGaoNWx8gxpgqvHm48Nu2v0VNgBsWHO56DKz386aTpIiZHavLTq3Rcc8 gOlh3xz95oA4Dvp0YWNYgJTi9srzzGB3otJoTi31dEJQMB4EoSxlcP3QFcYD+OlHGq4E SrSP3y+hTA0mxCdXlN+PoRE3NrwCVoXlvI4P+52R6wZod95/ArjPAuUXtbFs1hzjzvXV GcAQ==
X-Gm-Message-State: AFeK/H0KEoAFE3dWhq2ibjb6AKvHm4oDrOM9BzDP4DVNfrf68cJMDTyc9s3ktZTG/78mAw==
X-Received: by 10.107.5.139 with SMTP id 133mr24564654iof.107.1491338107237; Tue, 04 Apr 2017 13:35:07 -0700 (PDT)
Received: from [172.16.11.95] (50-76-68-137-static.hfc.comcastbusiness.net. [50.76.68.137]) by smtp.gmail.com with ESMTPSA id e20sm8924564itc.3.2017.04.04.13.35.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Apr 2017 13:35:06 -0700 (PDT)
Subject: Re: Detail in draft-ietf-6man-segment-routing-header-06
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
References: <ddf74f16-a2fb-64df-1f3f-e13b25d07c05@gmail.com> <12D80606-C8C2-47A2-A062-FF7EE95D776A@cisco.com>
Cc: 6man <ipv6@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <dd0b5675-2fc5-e12e-7173-c7bccdf7bd9b@gmail.com>
Date: Wed, 05 Apr 2017 08:35:07 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <12D80606-C8C2-47A2-A062-FF7EE95D776A@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/A7vy0akqv7S9NUt81fsha8Jg41I>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 20:35:10 -0000

Stefano,

Yes. But the draft does not specify the encapsulation method. So if
I was implementing this, I would have to guess. My guess is protocol
41 but I might be wrong. At the moment the draft is underspecified.

    Brian
On 05/04/2017 02:02, Stefano Previdi (sprevidi) wrote:
> the SRH draft specifies that the SRH is added to the packet by the packet source:
> 
> . an ingress router receives an incoming ipv6 packet
> . such packet is encapsulated into an outer IPv6 header
> . an SRH is then added to the outer encapsulation
> 
> the SRH draft doesn’t describe the case where the SRH is inserted by a core transit node. Such use-case is described in draft-voyer-6man-header-insertion.
> 
> s.
> 
> 
>> On Apr 4, 2017, at 3:43 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>
>> Hi,
>>
>> Unless I've missed it, draft-ietf-6man-segment-routing-header-06
>> doesn't actually specify the encapsulation mechanism mentioned
>> in section 5.1 and elsewhere.
>>
>> Will it simply be IPv6-in-IPv6 using header type 41 [RFC2473]?
>>
>> Regards
>>   Brian Carpenter
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>

v2.23.0 | Report a Bug | By Email