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

Teemu Savolainen <tsavo.stds@gmail.com> Thu, 19 September 2013 20:40 UTC

Return-Path: <tsavo.stds@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 27F8C21F893E for <v6ops@ietfa.amsl.com>; Thu, 19 Sep 2013 13:40:30 -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=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, NO_RELAYS=-0.001]
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 JzmvMFeVZrq7 for <v6ops@ietfa.amsl.com>; Thu, 19 Sep 2013 13:40:29 -0700 (PDT)
Received: from mail-ve0-x22e.google.com (mail-ve0-x22e.google.com [IPv6:2607:f8b0:400c:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id E839F21F88FB for <v6ops@ietf.org>; Thu, 19 Sep 2013 13:40:28 -0700 (PDT)
Received: by mail-ve0-f174.google.com with SMTP id jy13so7159133veb.5 for <v6ops@ietf.org>; Thu, 19 Sep 2013 13:40:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ZCL95t0Za+0U7Sr+autaDPD79Tk2dKuE8q2iWCfSoKg=; b=MhB05lF1rvJj876XP4WhFZAwLo2+Ems/raX5gl7ozC0wgYSSy77kwY9kYsfHgLmT+0 XLZ1oDRpQmQ1wJd0VZ9L4kfzhk86cPgqb+yBKiOmVEU3Kg25Uw8IxQ+0gTC1lTf+WXjW Q6IUAeDKxpKKF2U7uGzJmLf5mZ4eGU6j9Npr9asVyrQqtEUUEAJDIHPEQ4W5Nbjz5XS1 aQG+7pePcRpUAi9Ftx4FFXByREBAg7jECdW5AxQpmOO6djIWgBWns/T1w5WoeEJ1plVY SXueQrGbeu/Z9WRlRGblxXHzEWOMq37MNJCw7259oVhc8y5+uV6pqne/qY81cKp4qEA+ WcyQ==
MIME-Version: 1.0
X-Received: by 10.58.137.167 with SMTP id qj7mr2652903veb.1.1379623217749; Thu, 19 Sep 2013 13:40:17 -0700 (PDT)
Received: by 10.52.166.72 with HTTP; Thu, 19 Sep 2013 13:40:17 -0700 (PDT)
Received: by 10.52.166.72 with HTTP; Thu, 19 Sep 2013 13:40:17 -0700 (PDT)
In-Reply-To: <AFAB9759B1DE4F4187483FC509B501990115CC3ACBF7@HE111490.emea1.cds.t-internal.com>
References: <5236a1bc.82a8700a.3a3f.ffffc0d8@mx.google.com> <1379541548.63737.YahooMailNeo@web142504.mail.bf1.yahoo.com> <AFAB9759B1DE4F4187483FC509B501990115CC3ACBF7@HE111490.emea1.cds.t-internal.com>
Date: Thu, 19 Sep 2013 23:40:17 +0300
Message-ID: <CABmgDzRGteFt1-s0V1qD1m9f7_aZHEXfmbYkD6Nv2xoXEz6EFQ@mail.gmail.com>
From: Teemu Savolainen <tsavo.stds@gmail.com>
To: holger.metschulat@telekom.de
Content-Type: multipart/alternative; boundary="047d7b677efad163bc04e6c28f39"
Cc: v6ops@ietf.org
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: Thu, 19 Sep 2013 20:40:30 -0000

The DNS handling might suite for draft-ietf-v6ops-mobile-device-profile
Section 4, but in my opinion not to this document as it is not within the
narrow scope.

Secondly, I don't agree DHCP server support is required, as the CE can
include the DNS addresses in RAs as specified in RFC6106.

Best regards,

Teemu
On Sep 19, 2013 9:41 PM, <holger.metschulat@telekom.de> wrote:

> Hello all,
>
> I believe this needs to be looked at. DNS server addresses are sent from
> the network to the mobile host ("CE" in this scenario) by outband 3GPP
> signalling and need to be queried by the CE OS driver from the radio chip.
>
> In order to convey the DNS information to the clients attached via the
> LAN, the CE performing 64share needs to handle the DHCP solicits and answer
> on the network's behalf because simply forwarding the DHCP solicits will
> not work at all (the network won't answer them).
>
> Holger
>
> -----Ursprüngliche Nachricht-----
> Von: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] Im Auftrag
> von Mark ZZZ Smith
> Gesendet: Mittwoch, 18. September 2013 23:59
> An: Teemu Savolainen; Tassos Chatzithomaoglou; v6ops@ietf.org
> Betreff: Re: [v6ops] draft-ietf-v6ops-64share WGLC
>
> +1
>
> This purpose here is to describe a work around to a limitation, not to
> specify how RAs/DHCPv6 are supposed to be generally used and what options
> are present in them. I don't think RA or DHCPv6 options that aren't
> essential or useful to this *specific* scenario should be mentioned at all.
> DNS in RAs is not special to or necessary to sharing a /64.
>
> Generally related to DHCPv6 option passing across a CE device (of which
> this would be one), I posted the following draft a while ago. I'd be
> interested in comments.
>
> "IPv6 CE Device DHCPv6 Option Transparency"
>
> http://tools.ietf.org/html/draft-smith-v6ops-ce-dhcpv6-transparency-00
>
>
>
>
>
> >________________________________
> > From: Teemu Savolainen <tsavo.stds@gmail.com>
> >To: Tassos Chatzithomaoglou <achatz@forthnetgroup.gr>; "v6ops@ietf.org"
> ><v6ops@ietf.org>
> >Sent: Monday, 16 September 2013 4:12 PM
> >Subject: Re: [v6ops] draft-ietf-v6ops-64share WGLC
> >
> >
> >
> >IMHO it is better to keep this draft focused solely on address sharing,
> and not to go to other configuration topic or other possible problems.
> >
> >Btw most often, as of now, the "original" DNS server addresses are
> received via link layer signaling (see
> http://www.ietf.org/id/draft-ietf-v6ops-rfc3316bis-06.txt section 2.10),
> and thus, for example, may need to be added to "proxied" RA.
> >
> >Best regards,
> >
> >Teemu
> >
> >________________________________
> > From: Tassos Chatzithomaoglou
> >Sent: 15.9.2013 23:20
> >To: v6ops@ietf.org
> >Subject: Re: [v6ops] draft-ietf-v6ops-64share WGLC
> >
> >Just a quick question...
> >
> >I don't see any reference of DNS servers under 3.1, only MTU & Prefix.
> >Shouldn't there be a bullet showing that DNS info (UE address as DNS
> proxy, or original through-RA/DHCPv6 DNS servers) should also pass on the
> LAN link?
> >
> >--
> >Tassos
> >
> >Fred Baker wrote on 15/9/2013 21:00:
> >> This is to initiate a two week working group last call of
> >> http://tools.ietf.org/html/draft-ietf-v6ops-64share.  Please read it
> >> now. If you find nits (spelling errors, minor suggested wording
> >> changes, etc), comment to the authors; if you find greater issues,
> >> such as disagreeing with a statement or finding additional issues
> >> that need to be addressed, please post your comments to the list.
> >>
> >> We are looking specifically for comments on the importance of the
> >> document as well as its content. If you have read the document and
> >> believe it to be of operational utility, that is also an important
> >> comment to make.
> >> _______________________________________________
> >> v6ops mailing list
> >> v6ops@ietf.org
> >> https://www.ietf.org/mailman/listinfo/v6ops
> >>
> >
> >_______________________________________________
> >v6ops mailing list
> >v6ops@ietf.org
> >https://www.ietf.org/mailman/listinfo/v6ops
> >
> >_______________________________________________
> >v6ops mailing list
> >v6ops@ietf.org
> >https://www.ietf.org/mailman/listinfo/v6ops
> >
> >
> >
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>