Re: [spring] [DMM] How Encoded SID should be placed in SL (SRv6-mobile-uplane)

"Kentaro Ebisawa" <ebiken.g@gmail.com> Wed, 30 August 2017 12:35 UTC

Return-Path: <ebiken.g@gmail.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D423133159; Wed, 30 Aug 2017 05:35:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 4klR9KP_z3L4; Wed, 30 Aug 2017 05:35:33 -0700 (PDT)
Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::231]) (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 49323133173; Wed, 30 Aug 2017 05:35:33 -0700 (PDT)
Received: by mail-pf0-x231.google.com with SMTP id l87so9116981pfj.1; Wed, 30 Aug 2017 05:35:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:cc:date:message-id:in-reply-to:references:reply-to :user-agent:mime-version; bh=ZgpdpUJXVI6vWu/MlYK4rj6y9Sjuth0dDtMG3MO+apY=; b=O1Cxny4W0yvDTkC3TB354oS5AbO3IB9WXTZukcUbHdUM9khyjlHaGvh5yQK3J933wo IaDT439KHWs31NneKUF9tTs94DG7MGej5Vg0UE/9sbPpSipUnT8Q1hLUCmqY59tneghR cJXECAu32bAfcn7TCAl75pWFYi2+HHTktOEPUBUQ3v+lYEVTal7FmGljRAiIlhfYVcql /EpoPlgDO2/ib8SiWIHoiHK8sGka6CUoOPEeEOMRemIyag8VvUnuqfaNZOIuJkzzAVC0 Z+8o86j91dJ+ekOvCd5VLbgXGxaiRTdi4J2IP6Q7zatHHciq85HWHakWM9dFnGIP/haV +3og==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:cc:date:message-id:in-reply-to :references:reply-to:user-agent:mime-version; bh=ZgpdpUJXVI6vWu/MlYK4rj6y9Sjuth0dDtMG3MO+apY=; b=dUfYcFLZ6Wrgpkbof1YLp5xzb4wX+zY4UKmfLb8UCARNuH9WanxR73jmMO681hadF6 /ji/RNz7NmphX+zEKJ7wLrIwP7qlu/4hU10u2qtnU5yzwOgog6Xgcg48H0B2lFowOZTx rJpvl9F2gb/cwANLGqw690Lh/Hp+35VL3Tnp+qDJk6n0SvRA4PUEf7LqTZxx4v7eZAgi ujVEvo4bEoeLTWXuHE/7JZDqeny3OJoJLCGJzeFihbIRVrQy91a3PO0eneXdZqnKsAlp rt0fBq/suDfUQMY6vFu09Mv6E4ODUrs2kZbxyj8EurrIJPIiE96ToGQRfJzCaFtecAtN jKJQ==
X-Gm-Message-State: AHYfb5jmk9QmRqJwg+sqhhdFaKNkzThv6V+DnExDc5QbgV8U+MX+gcbr P3Pra7Lzu9o4Nw==
X-Received: by 10.101.85.193 with SMTP id k1mr1419718pgs.88.1504096532606; Wed, 30 Aug 2017 05:35:32 -0700 (PDT)
Received: from [192.168.10.7] (122x210x140x66.ap122.ftth.ucom.ne.jp. [122.210.140.66]) by smtp.gmail.com with ESMTPSA id q13sm9740815pfk.6.2017.08.30.05.35.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 30 Aug 2017 05:35:31 -0700 (PDT)
From: Kentaro Ebisawa <ebiken.g@gmail.com>
To: Satoru Matsushima <satoru.matsushima@gmail.com>
Cc: dmm <dmm@ietf.org>, spring@ietf.org
Date: Wed, 30 Aug 2017 12:35:30 +0000
Message-Id: <em4eb50999-355f-4f66-998e-e8d7147229b2@ebiken-desktop>
In-Reply-To: <CAFwJXX7w4bKDX4MrCy40dygqhi015WpOX6=rpoj0hGvCh8G+Yg@mail.gmail.com>
References: <emf443bb9d-b30a-4226-b2ad-a3cd141e4241@ebiken-desktop> <emedf1d248-b431-4377-be6a-728eb11c34a0@ebiken-desktop> <CAFwJXX7w4bKDX4MrCy40dygqhi015WpOX6=rpoj0hGvCh8G+Yg@mail.gmail.com>
Reply-To: Kentaro Ebisawa <ebiken.g@gmail.com>
User-Agent: eM_Client/7.1.30646.0
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="------=_MBA09855CA-4991-44C4-826A-9BFF6C70E329"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/T-sXzGZDifoit0TIonYQo-hyUWU>
Subject: Re: [spring] [DMM] How Encoded SID should be placed in SL (SRv6-mobile-uplane)
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Aug 2017 12:35:35 -0000

Hi Satoru,

Thank you for the email replies and taking time for offline discussion.

Your explanation in the emails clarified my questions, and leaving a few 
notes below to share clarification made during the offline chat for 
others on the list.

* In the draft, SRv6-mobile-uplane, IPv4 client packets will use Encap 
and IPv6 packets will use Insert while traversing SRv6 network.
* For UL, Encoded SID will be SL[1]
     * Exist side of SRv6 and not on the interworking node in DL.
     * SL[0] is an end host on external network who MN is communicating 
with.
* "Locater of interwork" differes for UL and DL. (as mentioned in the 
draft)

Regards,
--
Kentaro Ebisawa <ebiken.g@gmail.com>

------ Original Message ------
From: "Satoru Matsushima" <satoru.matsushima@gmail.com>
To: "Kentaro Ebisawa" <ebiken.g@gmail.com>
Cc: "dmm" <dmm@ietf.org>; spring@ietf.org; "Matsushima Satoru" 
<satoru.matsushima@g.softbank.co.jp>
Sent: 2017/08/29 10:44:16
Subject: Re: [DMM] How Encoded SID should be placed in SL 
(SRv6-mobile-uplane)

>Hi Kentaro,
>
>I've replied to your previous mail that I hope it would answer to your 
>questions.
>
>On Tue, Aug 29, 2017 at 12:44 AM, Kentaro Ebisawa <ebiken.g@gmail.com> 
>wrote:
>>Hi,
>>
>> > Q2) Down Link packet (SRv6 to existing network)
>> > > When the endpoint receives packet and the active segment of the
>> > > packet indicates the SID, the endpoint pop the SRH of the SID, and
>> > ...
>> >
>> > IPv6 Src: Origin Host
>> > IPv6 Dst: SL[n]
>> > Segment Left = n
>> > SL[m] = Encoded SID
>> > SL[m+1] = Segment m+1
>> > SL[n] = Segment n
>>
>>Actually I think this differs for T.Insert case, where MN user packet 
>>is IPv6.
>># Unless I missed description that Stateless Interworking will always 
>>use encapsulation mode even if user packet is IPv6.
>
>In DL, Stateless Interworking uses encapsulation for original IPv6 
>packet with IPv4 and tunnel header.
>
>
>>
>>
>>IPv6 Src: Origin Host
>>IPv6 Dst: SL[n]
>>Segment Left = n
>>SL[0] = MN address
>>SL[1] = Encoded SID
>>SL[n] = Segment n
>>
>
>As I mentioned in the previous mail, SL indicates SL[1] at the 
>interworking node.
>
>
>>And interworking segment should behave like below.
>>
>>When the endpoint receives packet and the active segment of the
>>packet indicates the SID, the endpoint pop the SRH of the SID,
>> >> Set IPv6 destination address as SL[0] (MN's address), and
>>then the endpoint encaps the payload with the encoded information in
>>the SID which are tunnel identifier of tunnel header, source and
>>destination IPv4 address of IPv4 header described in Figure 3.
>
>
>Right, it looks more precise description to it. Thanks!
>
>
>>
>>Maybe having example packet headers described for each cases 
>>(encap/insert, User Packet = IPv4/IPv6) will help this makes more 
>>easier to understand.
>>
>
>Absolutely yes, it's helpful to understand. I'll update the I-D with 
>that example in next revision.
>
>Thanks,
>--satoru
>