Re: [dhcwg] Anyone interested in continuing draft-ietf-dhc-dhcpv6-prefix-pool-opt?

"Leaf Yeh" <leaf.yeh.sdo@gmail.com> Thu, 22 August 2013 15:47 UTC

Return-Path: <leaf.yeh.sdo@gmail.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 3AF5521F95A6 for <dhcwg@ietfa.amsl.com>; Thu, 22 Aug 2013 08:47:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 KuX2lInh3tOv for <dhcwg@ietfa.amsl.com>; Thu, 22 Aug 2013 08:47:48 -0700 (PDT)
Received: from mail-pb0-x236.google.com (mail-pb0-x236.google.com [IPv6:2607:f8b0:400e:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 5B8E521F9477 for <dhcwg@ietf.org>; Thu, 22 Aug 2013 08:47:48 -0700 (PDT)
Received: by mail-pb0-f54.google.com with SMTP id ro12so1964804pbb.27 for <dhcwg@ietf.org>; Thu, 22 Aug 2013 08:47:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=BRpTXAndG+fy2RekNaCE/4H2HEPHKKRin/15F8lNrzo=; b=bUqy2Qw5LD1IhmbI33gpU/WLzKy10aphY3J4pR+kIMMOet+2AzzZZTSdJ0Ky0/gNN6 vE6ieck9C5JAAQvJMm+xx+bhtkhb/qtujT9yD+gc0sp4YkZ7JUd8MGWdsZKVlETKGSxd TM0ZawyVUDOIrEviNiZbaFQCQBoa1djkh2wrm4yvxIB0Fpk582FL8jx1KKZVta0bFuI9 hN3URY0GAPv8ZBrQxx/kM7WW1g+AwNWGW4AzIQTaMRpmDXSYQGMBFmB9fp806NGF+fMB Lb0NFznjuwO7v8D0ni3CHsEcFS7vcp/XiAJaadPA92tFVlbBIdj7lOjvmoBKxjHWMvWi wvZw==
X-Received: by 10.66.25.232 with SMTP id f8mr16186292pag.25.1377186468014; Thu, 22 Aug 2013 08:47:48 -0700 (PDT)
Received: from PC ([111.193.212.125]) by mx.google.com with ESMTPSA id os4sm15642616pbb.25.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 22 Aug 2013 08:47:47 -0700 (PDT)
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Sten Carlsen'" <stenc@s-carlsen.dk>, "'Bernie Volz \(volz\)'" <volz@cisco.com>
References: <52123110.10205@gmail.com> <94C682931C08B048B7A8645303FDC9F36EEDD8B410@PUEXCB1B.nanterre.francetelecom.fr> <5214BF85.8020509@gmail.com> <8D23D4052ABE7A4490E77B1A012B63077525FA8A@mbx-01.win.nominum.com> <CAC8QAcfaT2c3j1aFS0Qf2bieRs_MH1xov7CjE0POhMnU75YuiA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077525FDB5@mbx-01.win.nominum.com> <5215ee1f.a2c4440a.63af.10d6@mx.google.com> <5215FAF6.6060405@s-carlsen.dk> <521610a4.0466420a.469b.ffff9582@mx.google.com> <489D13FBFA9B3E41812EA89F188F018E186A66DC@xmb-rcd-x04.cisco.com> <52161C50.1010407@s-carlsen.dk>
In-Reply-To: <52161C50.1010407@s-carlsen.dk>
Date: Thu, 22 Aug 2013 23:47:40 +0800
Message-ID: <521632a3.4484440a.6478.5075@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac6fQadewU/2eW0NS0Sb0MIC1ZX4IQADCOUg
Content-Language: zh-cn
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Anyone interested in continuing draft-ietf-dhc-dhcpv6-prefix-pool-opt?
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, 22 Aug 2013 15:47:49 -0000

Sten - ."snooping" is normally used to describe that you look into/listen to
things that are not really meant for you.

I regard your understanding (or definition) is right.

Sten - . giving information meant for consumption at that point could
provide better information than deducting what you need from information
that does not really contain what you may need.

OPTION_PREFIX_POOL defined in this draft is targeted to the information
consumption point (or the relay agent @ PE router), which contains the
information of prefix pool (maintained by the server) for the aggregation
route.


Best Regards,
Leaf



----------------------------------------------------------------------
From: Sten Carlsen [mailto:stenc@s-carlsen.dk] 
Sent: Thursday, August 22, 2013 10:13 PM
To: Bernie Volz (volz)
Cc: Leaf Yeh; dhcwg@ietf.org
Subject: Re: [dhcwg] Anyone interested in continuing
draft-ietf-dhc-dhcpv6-prefix-pool-opt?

Also my understanding, "snooping" is normally used to describe that you look
into/listen to things that are not really meant for you.

My point was that giving information meant for consumption at that point
could provide better information than deducting what you need from
information that does not really contain what you may need.

On 22/08/13 15:33, Bernie Volz (volz) wrote:
Leaf ... the relay technically isn't snooping. It is relaying (it has to
process these messages -- they are not just going through the relay). The
snooping part is that it is looking inside the client part of the message.
This was what agentopt was trying to avoid (and also trying to permit
slightly different information going to the relay -- not just what went to
the client).

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of
Leaf Yeh
Sent: Thursday, August 22, 2013 9:23 AM
To: 'Sten Carlsen'; dhcwg@ietf.org
Subject: Re: [dhcwg] Anyone interested in continuing
draft-ietf-dhc-dhcpv6-prefix-pool-opt?

Sten - ... snooping sounds to me like a stop gap solution .

Per my understanding about the implementation (or behavior) of the PE router
of today, it (or it's CPU) snoops & handles every protocol message in the
control (and management) plane in fact.


Best Regards,
Leaf



----------------------------------------------------------------------------
------------------------------------------------------
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of
Sten Carlsen
Sent: Thursday, August 22, 2013 7:50 PM
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Anyone interested in continuing
draft-ietf-dhc-dhcpv6-prefix-pool-opt?

I may easily be wrong here but snooping sounds to me like a stop gap
solution i.e. what you do when no better method is available?

Seen from outside (my chair) it looks like there might be a need for a
protocol to talk directly with the switch/router, possibly first passing a
control/admin system that controls what may be set up in various places in
the network.

On 22/08/13 12:55, Leaf Yeh wrote:
Ted - This is a completely different situation-DHCP relay agents _already_
snoop DHCP messages to set up routing between PE and CPE devices.

I remember Ted has a discussion with WG-RTGWG on this topic in its session
of IETF84, and we had an additional discussion on the ML of
Routing-Discussion. Per these discussion records before and the personal
feedback from Adrian (RTG-AD), my conclusion (or impression) sounds that
'use DHCPv6 to add & withdraw route on the PE router' will get rough
consensus (or will not irritate big controversy) in IETF.


Best Regards,
Leaf



-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of
Ted Lemon
Sent: Thursday, August 22, 2013 12:29 AM
To: <sarikaya@ieee.org>rg>; Behcet Sarikaya
Cc: <dhcwg@ietf.org>
Subject: Re: [dhcwg] Anyone interested in continuing
draft-ietf-dhc-dhcpv6-prefix-pool-opt?

On Aug 21, 2013, at 9:00 AM, Behcet Sarikaya <sarikaya2012@gmail.com> wrote:
Isn't it not good to use DHCP options to establish routes? Remember what
happened to

It's not possible to get IETF consensus on a DHCP option to deliver routes
to clients.   I never said it was an inherently bad idea.   The reason I
asked MIF to stop working on it was that the endless floggings were getting
in the way of doing real work.   Really, preventing us from doing real work
at all.

This is a completely different situation-DHCP relay agents _already_ snoop
DHCP messages to set up routing between PE and CPE devices.

_______________________________________________
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


--
Best regards

Sten Carlsen

No improvements come from shouting:

       "MALE BOVINE MANURE!!!" 

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


-- 
Best regards

Sten Carlsen

No improvements come from shouting:

       "MALE BOVINE MANURE!!!"