[Dime] Suresh Krishnan's No Objection on draft-ietf-dime-rfc4006bis-11: (with COMMENT)

Suresh Krishnan <suresh@kaloom.com> Mon, 27 August 2018 15:01 UTC

Return-Path: <suresh@kaloom.com>
X-Original-To: dime@ietf.org
Delivered-To: dime@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 912E6130DFD; Mon, 27 Aug 2018 08:01:54 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Suresh Krishnan <suresh@kaloom.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-dime-rfc4006bis@ietf.org, Jouni Korhonen <jouni.nospam@gmail.com>, dime-chairs@ietf.org, jouni.nospam@gmail.com, dime@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.83.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153538211458.30033.3766934915165411264.idtracker@ietfa.amsl.com>
Date: Mon, 27 Aug 2018 08:01:54 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/NWPo4ZmmDURIq0IcpfAPvugLI-w>
Subject: [Dime] Suresh Krishnan's No Objection on draft-ietf-dime-rfc4006bis-11: (with COMMENT)
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.27
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Aug 2018 15:01:55 -0000

Suresh Krishnan has entered the following ballot position for
draft-ietf-dime-rfc4006bis-11: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dime-rfc4006bis/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for addressing my DISCUSS point.

Section 8.65

Any reason you are allowing encoding an IPv4 address as a IPv4-Mapped IPv6
Address while you can directly use address family 1 to encode it directly as an
IPv4 address? This allows for two different encodings for the same address.