Re: [dhcwg] SOL MAX RT

"Bernie Volz (volz)" <volz@cisco.com> Thu, 13 September 2012 12:17 UTC

Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B69721F8462 for <dhcwg@ietfa.amsl.com>; Thu, 13 Sep 2012 05:17:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.449
X-Spam-Level:
X-Spam-Status: No, score=-10.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1rlGynuOuHPa for <dhcwg@ietfa.amsl.com>; Thu, 13 Sep 2012 05:17:32 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 49DA121F845B for <dhcwg@ietf.org>; Thu, 13 Sep 2012 05:17:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2066; q=dns/txt; s=iport; t=1347538652; x=1348748252; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=NHRB/TPbCWN88bhLMkKJmgz9Rx1Lvy8fXA8boHVhpro=; b=mIRp989Pm05st0rtZPP6Tmf0SV7Zcc7vL4JgmSH6PhDae6PbrjwVEeax xl0zfF33mN2WcM53oBu9elMSWQM61IgiVA1IGFy4wNLf0UuAvn+kt/dn6 Nv7HAkPAXYofBw0UmDGVGzhIUnUDS5nIirukEtsT4siwFPMfUMRt40S+3 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAK3OUVCtJV2b/2dsb2JhbABCA7tvgQeCIAEBAQMBAQEBDwEnNAsFBwQCAQgRBAEBAR4JBycLFAkIAgQOBSKHZQYLm2mgOosQgxOCRGADlV+ONoFpgmY
X-IronPort-AV: E=Sophos;i="4.80,416,1344211200"; d="scan'208";a="120959317"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-1.cisco.com with ESMTP; 13 Sep 2012 12:17:32 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q8DCHVVL013987 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 13 Sep 2012 12:17:31 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.159]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.02.0298.004; Thu, 13 Sep 2012 07:17:31 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Wuyts Carl <Carl.Wuyts@technicolor.com>
Thread-Topic: [dhcwg] SOL MAX RT
Thread-Index: AQHNkR0BaQGOcCBbNkS5TFR4leqD8ZeH0D7wgABhBpU=
Date: Thu, 13 Sep 2012 12:17:31 +0000
Message-ID: <4C08562B-0B94-48EC-9651-193143EF4BDF@cisco.com>
References: <867F4B6A1672E541A94676D556793ACD16E4DC56E6@MOPESMBX01.eu.thmulti.com> <BD87928F6BFAEF4EBEB883E1C4F587723023AB16@PACDCEXMB01.cable.comcast.com>, <867F4B6A1672E541A94676D556793ACD16E4E8D555@MOPESMBX01.eu.thmulti.com>
In-Reply-To: <867F4B6A1672E541A94676D556793ACD16E4E8D555@MOPESMBX01.eu.thmulti.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19180.005
x-tm-as-result: No--47.666900-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] SOL MAX RT
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Sep 2012 12:17:33 -0000

If you want to make it proprietary, use a Vendor Information Option (17).

Sent from my iPad

On Sep 13, 2012, at 2:36 AM, "Wuyts Carl" <Carl.Wuyts@technicolor.com> wrote:

> Thx John,
> 
> Thing is that it get referred to from RFC6204, making it impossible for a CPE to meet the requirement of course.  We could take a proprietary option, but then every implementation would/could use a different number, which is to avoid I'd say.  In fact, this already happened before with DSLite option.  I've bumped into some implementation some time ago which was using a different number for the DSLite option, hence making the setup fail initially. 
> 
> Regs
> Carl
> 
> 
> 
> 
> -----Original Message-----
> From: Brzozowski, John [mailto:John_Brzozowski@Cable.Comcast.com] 
> Sent: woensdag 12 september 2012 21:29
> To: Wuyts Carl
> Cc: dhc WG
> Subject: Re: [dhcwg] SOL MAX RT
> 
> Carl,
> 
> I do not think this is possible, I will check and get back to you unless someone beats me to it on the list.
> 
> John
> =========================================
> John Jason Brzozowski
> Comcast Cable
> m) +1-609-377-6594
> e) mailto:john_brzozowski@cable.comcast.com
> o) +1-484-962-0060
> w) http://www.comcast6.net
> =========================================
> 
> On Sep 4, 2012, at 7:08 AM, Wuyts Carl wrote:
> 
>> All,
>> 
>> Anyone an idea when an option number will be assigned for this oro (as it still says TBD in below draft) ?
>> (I-D.droms-dhc-dhcpv6-solmaxrt-update)
>> 
>> Thx and regs
>> Carl
>> 
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg