Re: [v6ops] I-D Action:draft-ietf-v6ops-ipv6-cpe-router-bis-00.txt

"Don Sturek" <d.sturek@att.net> Tue, 15 March 2011 21:19 UTC

Return-Path: <d.sturek@att.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C880F3A6B44 for <v6ops@core3.amsl.com>; Tue, 15 Mar 2011 14:19:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.412
X-Spam-Level:
X-Spam-Status: No, score=-0.412 tagged_above=-999 required=5 tests=[AWL=0.138, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MSGID_MULTIPLE_AT=1.449, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gT+qRFUdjwTh for <v6ops@core3.amsl.com>; Tue, 15 Mar 2011 14:19:01 -0700 (PDT)
Received: from nm2-vm0.bullet.mail.bf1.yahoo.com (nm2-vm0.bullet.mail.bf1.yahoo.com [98.139.213.127]) by core3.amsl.com (Postfix) with SMTP id 904413A6B1F for <v6ops@ietf.org>; Tue, 15 Mar 2011 14:19:01 -0700 (PDT)
Received: from [98.139.212.153] by nm2.bullet.mail.bf1.yahoo.com with NNFMP; 15 Mar 2011 21:20:24 -0000
Received: from [98.139.212.212] by tm10.bullet.mail.bf1.yahoo.com with NNFMP; 15 Mar 2011 21:20:24 -0000
Received: from [127.0.0.1] by omp1021.mail.bf1.yahoo.com with NNFMP; 15 Mar 2011 21:20:24 -0000
X-Yahoo-Newman-Id: 266306.55251.bm@omp1021.mail.bf1.yahoo.com
Received: (qmail 30433 invoked from network); 15 Mar 2011 21:20:24 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1300224024; bh=HSW33NFT72QgO+QvduSHXRHW8ga/KCmrC99MZM9Pjk8=; h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Reply-To:From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language; b=ImDE5SyJleDDkVNSPF27k2WzIgpL5br4sZEecNiihbi8UZf3pU4pefifwwZaifkl4DGd3riwGjHUoEZBrq+Q1nI+k4XDYaIVmp2AyzR56U3zuA8rGotjVJCHa5gsE2hCSgS1MJmHGPj0gFrg+8JatM6NYGEady0/uuctbQcov7o=
Received: from Studio (d.sturek@174.78.56.227 with login) by smtp110.sbc.mail.bf1.yahoo.com with SMTP; 15 Mar 2011 14:20:23 -0700 PDT
X-Yahoo-SMTP: fvjol_aswBAraSJvMLe2r1XTzhBhbFxY8q8c3jo-
X-YMail-OSG: 9CO0a28VM1kwhFLv4fwB0_KoKczLAFtDzz25D3YrdrZTbE0 qHVBVK2myYtyCfMCodGSpjRsMINMKsJ8JX3I8MUeZaLSC4UAGXa0or58Rnnj HPL2v5w0tKBFegrZeB3Od3x1cnfnWL13u4phMGBroyj0NtRB1XJUekZMFd5d UYBPBa6oqSSPhI1vgYIEF9iVrzJPr8k.96.TQkO6NYnHP1kh6AWPg7469COy R5KRmi.pbYjO9mHg80HqBSFjNXxYx.j3v5aC8gRPF5Gutqu16gTTj7njO9e2 Gpd2gu5lDJ53Q1vfW
X-Yahoo-Newman-Property: ymail-3
From: Don Sturek <d.sturek@att.net>
To: "'Hemant Singh (shemant)'" <shemant@cisco.com>, 'james woodyatt' <jhw@apple.com>, 'IPv6 Ops WG' <v6ops@ietf.org>
References: <20110305184502.18531.25548.idtracker@localhost><76C43B2A-FEE5-4328-AB05-A10C38B23B2C@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C3F8B93C@XMB-RCD-109.cisco.com><C895B643-E461-4191-BAC3-EF735311F2F0@apple.com><5B6B2B64C9FE2A489045EEEADDAFF2C3F8B9B0@XMB-RCD-109.cisco.com><E76372ED-41A1-4987-9ECF-888B285DD606@apple.com><4D7E685A.80202@bogus.com><5B6B2B64C9FE2A489045EEEADDAFF2C301049872@XMB-RCD-109.cisco.com> <F0D4FEF4-D308-4DDE-B84C-2FFCE60B9376@apple.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3010499AA@XMB-RCD-109.cisco.com> <000a01cbe353$5e325a20$1a970e60$@sturek@att.net> <5B6B2B64C9FE2A489045EEEADDAFF2C3010499C9@XMB-RCD-109.cisco.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C3010499C9@XMB-RCD-109.cisco.com>
Date: Tue, 15 Mar 2011 14:20:19 -0700
Message-ID: <002001cbe356$ca9e3690$5fdaa3b0$@sturek>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcvjUPgF4bdZzDciQU6+FzmuDY0wHAAAE+2gAABjBhAAAEEHIAAARHwA
Content-Language: en-us
Cc: "'Simpson, Robby (GE Energy Services)'" <robby.simpson@ge.com>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-ipv6-cpe-router-bis-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: d.sturek@att.net
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 15 Mar 2011 21:19:02 -0000

Hi Hemant,

Yes, let's find some time for sure.  We have a draft proposal to discuss
with Stuart Cheshire on extending m-DNS for site local multicasts
(http://datatracker.ietf.org/doc/draft-lynn-dnsext-site-mdns/) plus we are
working on a white paper covering the following topics (note the white paper
is for discussion and portions may make sense for incorporation into the
advanced CPE requirements draft):

1)    White paper to address allocation of ULA prefixes, ULA address
autoconfiguration and DAD, rules on limiting propagation of ULA prefixes
beyond residence boundaries
      a. Define location where the ULA prefix is generated (default values
if we can agree to them also)
      b. Define mechanism to distribute ULA prefixes
      c. Define mechanism to create unique ULA addresses from prefix (or
more likely point to other drafts which do this like Autoconf)
      d. Define mechanism to stop propagation of ULA prefixes (which is
probably the start of a much more complex problem)
      e. Propose either delegation (and realignment/DAD of updated ULA
addresses) or a proxy and proxy agent to interconnect different ULA domains
in a residence

3)      White paper to define how an LBR (6LoWPAN border router) gets it
global prefix to use (from the prefix space of the subscriber network).    
      a.   Probably use DHCP on the LBR to allocate the prefix from the
subscriber network.

As soon as our schedule is known, I will drop you a note and see if we can
get together for 1-2 hours to discuss.

Don


-----Original Message-----
From: Hemant Singh (shemant) [mailto:shemant@cisco.com] 
Sent: Tuesday, March 15, 2011 2:01 PM
To: d.sturek@att.net; james woodyatt; IPv6 Ops WG
Subject: RE: [v6ops] I-D Action:draft-ietf-v6ops-ipv6-cpe-router-bis-00.txt

Don,

Good to hear from you.  I am also attending the IETF in Prague. I'd be
happy to sit down with you guys again (like we did in Beijing) and work
out the issues. 

Hemant

-----Original Message-----
From: Don Sturek [mailto:d.sturek@att.net] 
Sent: Tuesday, March 15, 2011 4:56 PM
To: Hemant Singh (shemant); 'james woodyatt'; 'IPv6 Ops WG'
Subject: RE: [v6ops] I-D
Action:draft-ietf-v6ops-ipv6-cpe-router-bis-00.txt

Hi Hermant,

Both Tom Herbst and myself (Don Sturek, representing Pacific Gas and
Electric) will be in Prague and would like to discuss further the CPE
Enhancements draft and the requirements around internetworked CPE within
a
home.

As outlined in the
http://tools.ietf.org/html/draft-herbst-v6ops-cpeenhancements-00 draft,
activities are underway to deploy IPv6 enabled smart meters as well as
support in WiFi and HomePlug to internetwork these smart meters with
existing home networks connected to existing ISPs.

The scenarios described in the draft are a little more than a year from
large scale deployment (11 million smart meters installed to date)

Don


-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
Of
Hemant Singh (shemant)
Sent: Tuesday, March 15, 2011 1:48 PM
To: james woodyatt; IPv6 Ops WG
Subject: Re: [v6ops] I-D
Action:draft-ietf-v6ops-ipv6-cpe-router-bis-00.txt



-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
Of james woodyatt
Sent: Tuesday, March 15, 2011 4:38 PM
To: IPv6 Ops WG
Subject: Re: [v6ops] I-D
Action:draft-ietf-v6ops-ipv6-cpe-router-bis-00.txt


>Huh?  Where is the draft that documents this?

http://tools.ietf.org/html/draft-herbst-v6ops-cpeenhancements-00

Snipped from the Abstract of the document above, is this text between
squared brackets.

[WiFi access points, cable boxes and other home devices with internet
access could all be internetworked with smart metering devices by
customers with no data networking expertise resulting in a complex
multi-segment network with differing prefixes, routing support and
service discovery needs.]

I am sure there is other text in the document that points out two
different routers in the home connected to two different SPs (one SP is
the home's DSL or broadband SP and the other SP is the Power Grid
company with their IPv6 CE router for the home) and thus one has a
multihomed home.  Anyway, you should look at Tom Herbst's prezo given to
the v6ops at the IETF79 in Beijing that clearly shows a multihomed
network.  Note also that multihomed involves both a multihomed WAN and
LAN for CE Router.

Hemant
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops