Re: Last Call: <draft-ietf-mboned-64-multicast-address-format-01.txt> (IPv4-Embedded IPv6 Multicast Address Format) to Proposed Standard

SM <sm@resistor.net> Sat, 21 April 2012 23:33 UTC

Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A8E811E8075; Sat, 21 Apr 2012 16:33:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.531
X-Spam-Level:
X-Spam-Status: No, score=-102.531 tagged_above=-999 required=5 tests=[AWL=0.068, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 JYn4HXQjBAjY; Sat, 21 Apr 2012 16:33:51 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id AB1F011E8076; Sat, 21 Apr 2012 16:33:51 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q3LNXjOS028733; Sat, 21 Apr 2012 16:33:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1335051231; i=@resistor.net; bh=RVsQHXSpJ8W7nE9Wji1zWLmSktJ2syxowdOblUYCg5g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=PXTZNeq1SXuKmoAqw5iCb6nT15W1lV2VcdSGw6BfHqF0xOWEb36M8QSD/h3muYBMF pBHSBXoXaNTYQ7swK4V0uFi6ujCnXA2K1FHISCap24hMoMKFWohReMhdPzba/YBrQA 2iOW3ru6iMdIDD41ropnYLOiJbMrOdaCOj6PiIvE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1335051231; i=@resistor.net; bh=RVsQHXSpJ8W7nE9Wji1zWLmSktJ2syxowdOblUYCg5g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=fu4pZMIXiVdSc3IJ7ugHnEno1XIcYoe82zYw9WE0TqjlayC1sx3R0o5y7UJKwEwSB jou1R1XrulT1tO/RKXLFhZAB+IOiqZaaFMJ7tqLRomiIHACsIe8jk8ewP6PNzX6e11 2cgT11rAqFCClcfJ7Hx9Am09pImUkXe92wY06i84=
Message-Id: <6.2.5.6.2.20120421154344.0c56be40@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 21 Apr 2012 16:26:23 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-mboned-64-multicast-address-format-01.txt> (IPv4-Embedded IPv6 Multicast Address Format) to Proposed Standard
In-Reply-To: <20120418223348.8411.8077.idtracker@ietfa.amsl.com>
References: <20120418223348.8411.8077.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: mboned@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Apr 2012 23:33:57 -0000

At 15:33 18-04-2012, The IESG wrote:
>The IESG has received a request from the MBONE Deployment WG (mboned) to
>consider the following document:
>- 'IPv4-Embedded IPv6 Multicast Address Format'
>   <draft-ietf-mboned-64-multicast-address-format-01.txt> as a Proposed
>Standard
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2012-05-02. Exceptionally, comments may be

Is there a write-up for this proposal?

In Section 2:

   "The format to build such addresses is defined in Section 3 for
    ASM mode and Section 4 for SSM mode."

I suggest expanding ASM and SSM on first use.

In Section 3:

   "To meet the requirements listed in Appendix A.2"

Wouldn't it be better to reference RFC 4291?

   "This field must follow the recommendations specified in [RFC3306]
    if unicast-based prefix is used or the recommendations specified
    in [RFC3956] if embedded-RP is used."

Shouldn't that be a MUST?

In Section 4:

   "Flags must be set to 0011."

Is that a requirement?

   "The embedded IPv4 address SHOULD be in the 232/8 range [RFC4607].
    232.0.0.1-232.0.0.255 range is being reserved to IANA."

Why is this a SHOULD?  What does being reserved to IANA mean?

Although the proposal appears simple, I would suggest further review 
as it updates RFC 4291.

Regards,
-sm