Re: [v6ops] draft-ietf-v6ops-64share WGLC

Alexandru Petrescu <alexandru.petrescu@gmail.com> Mon, 23 September 2013 14:09 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9661621F9F8E for <v6ops@ietfa.amsl.com>; Mon, 23 Sep 2013 07:09:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.94
X-Spam-Level:
X-Spam-Status: No, score=-8.94 tagged_above=-999 required=5 tests=[AWL=0.709, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tJ-7RJnFId6J for <v6ops@ietfa.amsl.com>; Mon, 23 Sep 2013 07:09:23 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) by ietfa.amsl.com (Postfix) with ESMTP id C070521F9F88 for <v6ops@ietf.org>; Mon, 23 Sep 2013 07:09:22 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r8NE9LJ0010301 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <v6ops@ietf.org>; Mon, 23 Sep 2013 16:09:22 +0200
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r8NE9LgJ026827 for <v6ops@ietf.org>; Mon, 23 Sep 2013 16:09:21 +0200 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r8NE9IOt012812 for <v6ops@ietf.org>; Mon, 23 Sep 2013 16:09:21 +0200
Message-ID: <52404B8E.9020003@gmail.com>
Date: Mon, 23 Sep 2013 16:09:18 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: v6ops@ietf.org
References: <5236a1bc.82a8700a.3a3f.ffffc0d8@mx.google.com> <1379541548.63737.YahooMailNeo@web142504.mail.bf1.yahoo.com> <AFAB9759B1DE4F4187483FC509B501990115CC3ACBF7@HE111490.emea1.cds.t-internal.com> <CABmgDzRGteFt1-s0V1qD1m9f7_aZHEXfmbYkD6Nv2xoXEz6EFQ@mail.gmail.com> <1379624093.60428.YahooMailNeo@web142501.mail.bf1.yahoo.com> <CABmgDzTBoUzm=MRy5LkhwpbPRW23kCDStfcFCs-NBPR9mk9XJw@mail.gmail.com>
In-Reply-To: <CABmgDzTBoUzm=MRy5LkhwpbPRW23kCDStfcFCs-NBPR9mk9XJw@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Subject: Re: [v6ops] draft-ietf-v6ops-64share WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 23 Sep 2013 14:09:29 -0000

Le 19/09/2013 23:26, Teemu Savolainen a écrit :
>  > >Secondly, I don't agree DHCP server support is required, as the CE
> can include the DNS addresses in RAs as specified in RFC6106.
>  > >
>  >
>  > How could a CE convey NTP server settings to hosts using RAs?
> Accurate host time is pretty useful, if not essential.
>
> It cannot, but then again it probably would not help to have DHCP server
> implementation either, as, AFAIK, cellular networks commonly today do
> not provide DHCP service to terminals (to these "CEs" that would use
> 64share instead of DHCPv6 PD)....

In addition to considering whether or not the cellular network delivers 
DHCP, one should consider whether or not the local USB dongle delivers 
DHCP to the Host.

This or someone other unknown entity in the middle, between the network 
and the host, delivers DHCP and make that link look like ARP-capable 
link.  The QMI drivers and clients in linux see new evolutions in that 
sense.

But that is more like future work; 64share has place here where QMI is 
not yet widely deployed.

> If CE has no NTP settings, it cannot
> share them either. CE often gets time from cellular network, though.. So
> maybe CE should implement NTP server and with DHCP share its own address
> as NTP address?

CE to run a DHCPv6 Server?

> ... And this is why it is best to focus 64share to just prefix sharing;-)

In a sense I agree to let 64share just do the prefix sharing.

But obviously the client on the LAN side needs a way to get a DNS server 
address otherwise its connectivity is only partial.

Alex

>
> Best regards,
>
> Teemu
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>