Re: How to include APBP scenarios in the Coexistence RequirementI-D

marcelo bagnulo braun <marcelo@it.uc3m.es> Thu, 19 June 2008 16:03 UTC

Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AEFB53A6927 for <ietfarch-v6ops-archive@core3.amsl.com>; Thu, 19 Jun 2008 09:03:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.572
X-Spam-Level:
X-Spam-Status: No, score=-2.572 tagged_above=-999 required=5 tests=[AWL=-0.661, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, MIME_8BIT_HEADER=0.3, RCVD_BAD_ID=2.837, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5JR7VXQlm1J5 for <ietfarch-v6ops-archive@core3.amsl.com>; Thu, 19 Jun 2008 09:03:11 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id AFD993A69C9 for <v6ops-archive@lists.ietf.org>; Thu, 19 Jun 2008 09:01:33 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-v6ops@ops.ietf.org>) id 1K9MUw-0005di-BF for v6ops-data@psg.com; Thu, 19 Jun 2008 15:56:30 +0000
Received: from [163.117.176.131] (helo=smtp01.uc3m.es) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <marcelo@it.uc3m.es>) id 1K9MUq-0005ck-MT for v6ops@ops.ietf.org; Thu, 19 Jun 2008 15:56:27 +0000
Received: from marcelo-bagnulos-macbook-pro.local (74.pool85-53-142.dynamic.orange.es [85.53.142.74])by smtp01.uc3m.es (Postfix) with ESMTP id D6DAE6EEBEF;Thu, 19 Jun 2008 17:56:21 +0200 (CEST)
Message-ID: <485A819B.6010900@it.uc3m.es>
Date: Thu, 19 Jun 2008 17:56:11 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Rémi Després <remi.despres@free.fr>
CC: v6ops <v6ops@ops.ietf.org>, Fred Baker <fred@cisco.com>
Subject: Re: How to include APBP scenarios in the Coexistence RequirementI-D
References: <485A7117.4090206@free.fr>
In-Reply-To: <485A7117.4090206@free.fr>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-imss-version: 2.051
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-10.2685 TC:1F TRN:41 TV:5.5.1026(15982.000)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Remi,

as editor of the document, my task is to reflect the WG consensus in the 
document.
So far, i only see you supporting for this i.e. i haven't received any 
other comment on this respect.

So, if other people care to comment on this, and the WG express that 
they are ok with including this in the document, i would do that.

Regards, marcelo


Rémi Després escribió:
> Hi Marcello,
>
> You may not remember my e-mail of may 22:
> http://www.ops.ietf.org/lists/v6ops/v6ops.2008/msg00808.html,
>
> It dealt with the relationship between
> - my draft-despres-v6ops-apbp-00 (APBP)
> - your draft-ietf-v6ops-nat64-pb-statement-req-00
>
> Since the matter of the APBP I-D fits in the scope of your Requirement 
> I-D, I take the opportunity of a reminder to (hopefully) clarify the 
> subject.
>
>
> Your Requirement draft is about
>  "IPv4/IPv6 Coexistence and Transition: Requirements for solutions".
> Its scope, defined in the introduction, is:
>  "requirements for solutions to IPv4/IPv6 coexistence and eventual
> transition in a scenario in which dual stack operation is not the norm"
> It includes, among others, scenarios for:
> A. "an IPv4 system connecting to an IPv4 system across an IPv6
> network"
> B. "an IPv6 system connecting to an IPv4 system".
>
> Now, in the APBP draft:
> - Section 2 introduces a new scenario for A.
> - Section 5.2 introduces a new scenario for a variant of B (where the
> IPv6 system is modified to obtain E2E IPv4 transparency for IPv4/IPv6
> encapsulated packets)
>
> The purpose of these new scenarios is:
> - Scalability (scenario A)
> - E2E transparency (scenario B)
>
>
> To introduce visibility of these scenarios in your draft without too 
> much reorganization, I suggest this possibility:
>
> In your I-D,
>  " 2.1.2 Scenarios that do not require translation
>    2.1.3 Scenarios that require translation "
> would be replaced by:
>  " 2.1.2 Scenarios that do not require translation between IPv6 and IPv4
>      2.1.2.1 Scenarios based only on tunnels
>              <current 2.1.2 text>
>      2.1.2.1 Scenarios combining tunnels and address-port borrowing
>          < A text, not too long, I could volunteer to provide >
>    2.1.3 Scenarios that require translation between IPv6 and IPv4
>              <current 2.1.3 text > "
>
>
> The questions are then:
> - Is it agreed that something needs to be done? (And if not, what 
> objections need to be discussed)
> - If it is agreed, are there better ways to include APBP scenarios in 
> the Requirement I-D?
>
>
> Regards.
>
> Rémi
>
>