Re: [mif] Route option for DHCPv6 - next steps?

jouni korhonen <jouni.nospam@gmail.com> Wed, 25 April 2012 08:33 UTC

Return-Path: <jouni.nospam@gmail.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B515B21F879A for <mif@ietfa.amsl.com>; Wed, 25 Apr 2012 01:33:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 rWZJ0kkD9qxU for <mif@ietfa.amsl.com>; Wed, 25 Apr 2012 01:33:57 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 085F121F8799 for <mif@ietf.org>; Wed, 25 Apr 2012 01:33:56 -0700 (PDT)
Received: by lbgc1 with SMTP id c1so1304158lbg.31 for <mif@ietf.org>; Wed, 25 Apr 2012 01:33:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=b+dm0r0VuTYBHZ5LjGZTuIFO03d1RPdSuL4+Bgh9rgI=; b=rik/FUqzxnmBaN0uPF6O7t2C67stY4fwshWoxPL4/hiSpI+O/kxWMwb6jNNk3k8Jnj iMeQVj0uJ738GOr9mewF28c1ETzSJRN256krC2YB3B992RILWUqpYwCFDqfSAs0DMVuR yQdAXE9pP/gfDoXO9eE2hVQ3wAjYgpEQ1iHzjewzgPfERSbOBma32QdLT0yUS+3EzEO1 Q95e7R0LYtp5yibN86xGO7wF3/NphEVLbu1sNnkdLxFgYDYN90P+JdXaNyTdGmASxSem nlQ6+fjC+FlOJG/m5dWUzSWYK8U0h93eyoCf6N8nhxos3Q/8jjDujLegsN3Sv4AbzZkS YO4w==
Received: by 10.112.24.197 with SMTP id w5mr830404lbf.83.1335342835929; Wed, 25 Apr 2012 01:33:55 -0700 (PDT)
Received: from a88-114-173-83.elisa-laajakaista.fi (a88-114-173-83.elisa-laajakaista.fi. [88.114.173.83]) by mx.google.com with ESMTPS id q5sm27472458lbd.13.2012.04.25.01.33.40 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 25 Apr 2012 01:33:55 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: jouni korhonen <jouni.nospam@gmail.com>
In-Reply-To: <4F969A70.5090506@gmail.com>
Date: Wed, 25 Apr 2012 11:33:38 +0300
Content-Transfer-Encoding: 7bit
Message-Id: <6B411362-339E-47E4-B54E-EE02666D65A8@gmail.com>
References: <75459BC2-E733-45C0-BC1C-25A19BBA1137@gmail.com> <4F744831.3070406@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307472D4175@mbx-01.win.nominum.com> <4F7453FC.3010502@gmail.com> <4F74546D.4060808@gmail.com> <72C42575-6BE2-4F27-B7F4-AA4539DA7EF9@lilacglade.org> <8D23D4052ABE7A4490E77B1A012B6307472D43A1@mbx-01.win.nominum.com> <069301cd0dd2$5954df00$0bfe9d00$@tndh.net> <550B9F79-1642-469F-9ED3-96DA26AA40AB@lilacglade.org> <CAFFjW4hkGMm+mLSzpdWPcFLUcY3Hkyb+BDxh+5910YtfZxGD-A@mail.gmail.com> <CA+H2C9Zu3AS6aTxg1gebe0ZS2LXWmJjOPpbhaUHGZtXvF0UipQ@mail.gmail.com> <17F90720-AA1F-4F74-9598-2E5A5AC813CE@nttv6.net> <CAKD1Yr1s7SARfnowZV1uU=dDPi46-OjRQnM4otKsW3Y-k+84cw@mail.gmail.com> <F4D68CC2-27C5-4FB1-A11F-026E5261DB77@nttv6.net> <765F32AC-FBE3-4E8B-B698-1955C5601C2B@nominum.com> <4F96550E.6020709@gmail.com> <CAKD1Yr0d4ez4dogDk1gRvUHvWpoTBEg_4HatQQoa5oa3Yu9NFw@mail.gmail.com> <4F965BD2.1080906@gmail.com> <CAKD1Yr1=ry45uw=Xy1Gf5t30oC=ugzMGpwz7kbwctgXvg83WLw@mail.gmail.com> <4F969A 70.5090506@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: mif@ietf.org
Subject: Re: [mif] Route option for DHCPv6 - next steps?
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Apr 2012 08:33:58 -0000

On Apr 24, 2012, at 3:20 PM, Alexandru Petrescu wrote:

[snip]


>> As for #3: RFC 6204 doesn't specify any specific technology, and it's
>> certainly not limited to ADSL. Much of the behaviour it specifies is
>> equally applicable to CPEs whose uplink is a cellular link.
> 
> ?
> 
> 'CPE' is not a term used for the cellular links, I think. RFC6204 says
> 'residential or small-office router'. I think it is a stretch to claim
> that RFC6204 applies to cellular links. E.g. few if any cellular

RFC6204 is not necessarily the best fit for cellular (6204bis does it 
better) but it definitely does not preclude one making a compliant CE
device with a cellular WAN link.

> terminals use DHCP as of today, whereas RFC6204 would require them all
> to. Also, RFC6204 requires all cellular terminals to use Ethernet

So? You would most likely use your cellular just as a modem to connect
to network and the rest of the system & stack would be in the host side
of the CE. This is sometimes referred as the "split-UE" in 3GPP circles.

> encapsulation on their WAN interface whereas none actually does.

All WLL-* requirements start with "If the WAN interface supports.."
effectively making the following MUST conditional. Those MUSTs, like
for ethernet, apply only when the WAN implements the said technology.

> There is another RFC - 3316 - "IPv6 for some 2G and 3G Cellular Hosts"
> which relates more to cellular.

Or a bit more recent RFC6459..

- Jouni


> 
> Alex
> 
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif