Re: [Int-area] Main change in draft-ietf-intarea-provisioning-domains-03: connection sharing

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 25 October 2018 08:58 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A756812870E for <int-area@ietfa.amsl.com>; Thu, 25 Oct 2018 01:58:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 LdJHtUg84Mgd for <int-area@ietfa.amsl.com>; Thu, 25 Oct 2018 01:58:26 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D259130DFD for <int-area@ietf.org>; Thu, 25 Oct 2018 01:58:26 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w9P8wL8j103772; Thu, 25 Oct 2018 10:58:21 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5AD612029BC; Thu, 25 Oct 2018 10:58:21 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 4ABA320125C; Thu, 25 Oct 2018 10:58:21 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w9P8wLkl021375; Thu, 25 Oct 2018 10:58:21 +0200
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>, int-area <int-area@ietf.org>
References: <46F80B70-03CD-48C9-AF8E-404F9F827AFC@cisco.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <62a4bb09-2909-ec05-bd7e-f51f2a1deb98@gmail.com>
Date: Thu, 25 Oct 2018 10:58:20 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <46F80B70-03CD-48C9-AF8E-404F9F827AFC@cisco.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/nAH0I1zghXdqxtv7a4xJTg5C5Ck>
Subject: Re: [Int-area] Main change in draft-ietf-intarea-provisioning-domains-03: connection sharing
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2018 08:58:30 -0000


Le 24/10/2018 à 11:51, Eric Vyncke (evyncke) a écrit :
> The authors of this draft would like to have some discussions even 
> before the INTAREA WG meeting in two weeks. Especially on the major 
> change about connection sharing (tethering) where the authors spent 
> several hours on it.
> 
> See all differences in: 
> https://tools.ietf.org/rfcdiff?url2=draft-ietf-intarea-provisioning-domains-03.txt
> 
> The section 3.4.3 is about “Connection Sharing by the Host” and 
> currently is:
> 
> ------- start --------
> 
>     The situation when a host shares connectivity from an upstream
> 
>     interface (e.g. cellular) to a downstream interface (e.g.  WiFi) is
> 
>     known as 'tethering'.  Techniques such as ND-proxy [RFC4389 
> <https://tools.ietf.org/html/rfc4389>], 64share
> 
>     [RFC7278 <https://tools.ietf.org/html/rfc7278>] or prefix delegation 
> (e.g. using DHCPv6-PD [RFC3633 <https://tools.ietf.org/html/rfc3633>]) may
> 
>     be used for that purpose.
> 
>     Whenever the RAs received from the upstream interface contain a PVD
> 
>     RA option, hosts that are sharing connectivity SHOULD include a PVD
> 
>     Option within the RAs sent downstream with:
> 
>        The same PVD-ID FQDN.
> 
>        The same H-bit, Delay and Sequence Number values.
> 
>        The L bit set whenever the host is sharing IPv4 connectivity

I am not sure it is possible to 'share' IPv4 connectivity, in the same 
manner like sharing IPv6 connectivity.

There are no PVDs in IPv4, the 'sharing' is with NAT/DHCP, etc.

To achieve the same effect in IPv4 as in IPv6 (propagate info from 
upstream RA to downstream RA) one may need to specify:

- set in DHCP Advertise sent downstream the same DNS server as received
   in the DHCP Advertise from upstream.

Or maybe I dont understand the meaning of the L bit.  And I have to read 
the draft.

Alex

> 
>        received from the same upstream interface.
> 
>        The bits from the Reserved field set to 0.
> 
>     The values of the R-bit, Router Advertisement message header and
> 
>     Options field depend on whether the connectivity should be shared
> 
>     only with PvD aware hosts or not (see Section 3.2 
> <https://tools.ietf.org/html/draft-ietf-intarea-provisioning-domains-03#section-3.2>).  
> In particular,
> 
>     all options received within the upstream PvD option and included in
> 
>     the downstream RA SHOULD be included in the downstream PvD option.
> 
> ---- end ----
> 
> Comments are welcome before, during and after the WG meeting
> 
> -éric for all authors
> 
> 
> 
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
>