IETF Logo Mail Archive

Re: [v6ops] draft-bao-v6ops-rfc6145bis WGLC

<holger.metschulat@telekom.de> Tue, 01 December 2015 13:11 UTC

Return-Path: <holger.metschulat@telekom.de>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF9E31B2D15 for <v6ops@ietfa.amsl.com>; Tue, 1 Dec 2015 05:11:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.86
X-Spam-Level:
X-Spam-Status: No, score=-3.86 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jpIQzwLY4vuH for <v6ops@ietfa.amsl.com>; Tue, 1 Dec 2015 05:11:54 -0800 (PST)
Received: from tcmail93.telekom.de (tcmail93.telekom.de [80.149.113.205]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 597831B2D0F for <v6ops@ietf.org>; Tue, 1 Dec 2015 05:11:47 -0800 (PST)
Received: from s4de8nsazdfe010.bmbg.telekom.de ([10.175.246.202]) by tcmail91.telekom.de with ESMTP/TLS/DHE-RSA-AES128-SHA; 01 Dec 2015 14:11:20 +0100
X-IronPort-AV: E=Sophos;i="5.20,369,1444687200"; d="scan'208";a="786412127"
Received: from he111510.emea1.cds.t-internal.com ([10.206.92.113]) by q4de8nsa015.bmbg.telekom.de with ESMTP/TLS/AES128-SHA; 01 Dec 2015 14:11:17 +0100
Received: from HE111507.emea1.cds.t-internal.com ([10.206.92.89]) by HE111510.emea1.cds.t-internal.com ([::1]) with mapi; Tue, 1 Dec 2015 14:11:16 +0100
From: holger.metschulat@telekom.de
To: v6ops@ietf.org
Date: Tue, 01 Dec 2015 14:11:15 +0100
Thread-Topic: [v6ops] draft-bao-v6ops-rfc6145bis WGLC
Thread-Index: AdEq2Dx5SGv4nT8WRX6YRd+6UpCuFAApMpiQ
Message-ID: <88CAA5385EB5404392BF93106C8C53F8AED5357036@HE111507.emea1.cds.t-internal.com>
References: <201511291900.tATJ04fK009754@irp-lnx1.cisco.com>
In-Reply-To: <201511291900.tATJ04fK009754@irp-lnx1.cisco.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/0DSUcL3NvR0sCPzEKH46M_mYmq4>
Subject: Re: [v6ops] draft-bao-v6ops-rfc6145bis WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Dec 2015 13:11:58 -0000

Hello,

some comments:

- draft-anderson-v6ops-siit-eam is now on version 03, and in the RFC Editor queue - should RFC6145bis waint until the EAM RFC is published to get the references right?

- A.1 step 1 suggests that the IPv6 host must perform the formation of the IPv6 destination address from the IPv4 address of the peer on its own, knowing the address mapping algorithm. Should it be mentioned here that the mapping could have been done externally, e.g. by a AAAA DNS entry or inband signalling, so that the mapping algorithm does not need to be known on the v6 host (same applies for A.2)?

- 3.1: Translation of the Source and Destination Address: While the algorithms are stated, it is unclear to me what the translator should do if it finds a translation only for the source address, but not for the destination address, and vice versa? Section 5 says that RFC6052 is the default mapping, but this is a "SHOULD" so we could end up in a situation where not both source and destination address can be translated at the same time.

Holger



-----Ursprüngliche Nachricht-----
Von: v6ops [mailto:v6ops-bounces@ietf.org] Im Auftrag von fred@cisco.com
Gesendet: Sonntag, 29. November 2015 20:00
An: v6ops@ietf.org
Betreff: [v6ops] draft-bao-v6ops-rfc6145bis WGLC

This is to initiate a two week working group last call of http://tools.ietf.org/html/draft-bao-v6ops-rfc6145bis.  
Please read it now. If you find nits (spelling errors, minor suggested wording changes, etc), comment to the authors; if you find greater issues, such as disagreeing with a statement or finding additional issues that need to be addressed, please post your comments to the list.

We are looking specifically for comments on the importance of the document as well as its content. If you have read the document and believe it to be of operational utility, that is also an important comment to make.

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

v2.23.0 | Report a Bug | By Email