Re: [dhcwg] Some comments regarding draft-ietf-dhc-dhcpv6-unknown-msg-01

"Bernie Volz (volz)" <volz@cisco.com> Mon, 29 July 2013 09:14 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 3481C21F9AE2 for <dhcwg@ietfa.amsl.com>; Mon, 29 Jul 2013 02:14:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 Z3K66MPVLnEP for <dhcwg@ietfa.amsl.com>; Mon, 29 Jul 2013 02:14:37 -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 9237021F9966 for <dhcwg@ietf.org>; Mon, 29 Jul 2013 02:14:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13679; q=dns/txt; s=iport; t=1375089277; x=1376298877; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=WotizjiBuz0pBosuaVpn4UJYGMe8JSKXpgdjYx0WW+I=; b=W5pJbckE1fzePEIzK51loCcYgqyF3UZdwtnC8axc4w5j0JCikdNWLdEj 4cfe+6+8ykC8+xseA+HIbwFpSpYJdcICWuKAC9ByN2fw8gZkS2uaJFJEQ XVxjLhBqP3urjZsbVPrjZB2F1VpKNkikHgjnaYH78eSVw8QDO80K3GIwC Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgoFAOwx9lGtJV2c/2dsb2JhbABRCoMGNYNgukaBFRZ0giUBAQQBAQEeAUwLEAIBCCcYAgMCIQYLFBECBA4Fh34DDwyKcZtAAYguDYhaBI0VgS+BNQQHgmI2bwOVdoFpjCaFJoMU
X-IronPort-AV: E=Sophos; i="4.89,768,1367971200"; d="scan'208,217"; a="240521415"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-1.cisco.com with ESMTP; 29 Jul 2013 09:14:37 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r6T9Ebkr017305 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 29 Jul 2013 09:14:37 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.99]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.02.0318.004; Mon, 29 Jul 2013 04:14:36 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Qi Sun <sunqi.csnet.thu@gmail.com>
Thread-Topic: [dhcwg] Some comments regarding draft-ietf-dhc-dhcpv6-unknown-msg-01
Thread-Index: AQHOjDp6Y5trO2fg+0erLro62xl36Zl7X6JL
Date: Mon, 29 Jul 2013 09:14:36 +0000
Message-ID: <FDA28DBD-D84D-4B6E-A394-9BD7E90D5E54@cisco.com>
References: <CAFGoqUPOVNOknZFD7JkhOSDqu63VML6iH7yyuA-je-_8W=G2bQ@mail.gmail.com>, <A62A9726-FD37-4715-9073-480187798603@gmail.com> <59AC99E8-885D-4D18-9C4A-3AE649F9FA95@cisco.com>, <9EF31D11-CBF7-41FD-BB64-71D69FB015C1@gmail.com>
In-Reply-To: <9EF31D11-CBF7-41FD-BB64-71D69FB015C1@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_FDA28DBDD84D4B6EA3949BD7E90D5E54ciscocom_"
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "<cuiyong@tsinghua.edu.cn>" <cuiyong@tsinghua.edu.cn>, Ted Lemon <ted.lemon@nominum.com>
Subject: Re: [dhcwg] Some comments regarding draft-ietf-dhc-dhcpv6-unknown-msg-01
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: Mon, 29 Jul 2013 09:14:43 -0000

One example was the text about standards compliant server not sending msgs.

I really think keeping it much simpler to say a relay that receives a msg that is not a relay-forw, relay-reply, or other message explicitly intended to be processed by the relay as per some RFC should forward the message in a Relay-Forw.

Future documents may define messages that a relay must process (rather than forwarding), though existing relays will forward these until updated. Servers must drop packets that they are not to process.

That's about it.

- Bernie (from iPhone)

On Jul 29, 2013, at 11:03 AM, "Qi Sun" <sunqi.csnet.thu@gmail.com<mailto:sunqi.csnet.thu@gmail.com>> wrote:

Hi Bernie,

I wonder if reworking the draft a bit would be worthwhile. In some cases it makes statements that could be dangerous in the long run.

Would you please elaborate so that we could work on them?


Best Regards,
Qi Sun


On 2013-7-29, at 上午10:32, Bernie Volz (volz) wrote:

I wonder if reworking the draft a bit would be worthwhile. In some cases it makes statements that could be dangerous in the long run.

The basic concept is that a received msg is either forwarded or consumed by relay.

If the message is a Relay-forw or Relay-Reply, RFC 3315 explains how to handle it.

If not one of these and not one to be consumed by relay (ie, Reconfigure-Reply), it should be forwarded (Relay-forw) unless policy disallows (ie, not client facing interface).

- Bernie (from iPhone)

On Jul 29, 2013, at 10:08 AM, "Qi Sun" <sunqi.csnet.thu@gmail.com<mailto:sunqi.csnet.thu@gmail.com>> wrote:


Hi Marcin ,

Thanks for the review!

It would be good to distinguish between the term "intended recipient" and "recipient". From the context I understand that the intended recipient is used with regards to the target for the message being passed through relays and the recipient is a term used to describe a host which is currently holding a message. Perhaps this clarification could be placed in the glossary or somewhere in the text?

Consider this:
"... the message is valid for constructing a new Relay-forward message if the recipient is a relay agent, the relay agent does not identify itself as the intended recipient, and the message is not a Relay-Reply message".

There is a mix-up of these two terms which may suggest that the message is sent to a wrong relay which is  not an "intended recipient", while the sentence is actually meant to tell that the relay is not a target for the message being encapsulated.

How about the following text:

"... the message is valid for constructing a new Relay-forward message if a relay agent receives the message, but the relay agent does not identify itself as the target of the message, and the message is not a Relay-Reply message."

Is the usage of 'target' here is precise?

Best Regards,
Qi

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