IETF Logo Mail Archive

Re: [v6ops] New Version Notification for draft-anderson-v6ops-siit-eam-01.txt

Ca By <cb.list6@gmail.com> Mon, 08 December 2014 05:02 UTC

Return-Path: <cb.list6@gmail.com>
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 A02541A6ED8 for <v6ops@ietfa.amsl.com>; Sun, 7 Dec 2014 21:02:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 HHBVdH-T6yEh for <v6ops@ietfa.amsl.com>; Sun, 7 Dec 2014 21:02:53 -0800 (PST)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07B421A3BA7 for <v6ops@ietf.org>; Sun, 7 Dec 2014 21:02:53 -0800 (PST)
Received: by mail-wg0-f47.google.com with SMTP id n12so5289549wgh.20 for <v6ops@ietf.org>; Sun, 07 Dec 2014 21:02:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=j/DqOH7jg2D3GSCzlE8KMYLgwvOMGJdBLhSL9+TOKvg=; b=bX3CUlri4/fxJcMazAcM2eOyHn6tkgJrYzG8O5dYnfoytwu8fqss6Qe/GCTiIxt3Aj qdPV9KDyimVgedq41HXbIDAiFs9J7/AmvyAndqkHFA6lZJ3vzLlHLUEUC9SInApJcyDE g0vJu7HcRSxq62M5j6FrWQ62oWxzGbFovNHhmNFQPGv/3ZklS06wPZdzswArQ4CYDTAE /r+E04UpSg+GRgIHhNY19CXqF3V6JVU1yKsxZVE5AC/qB/hB3grVhJLKbggrEQhFcknQ A6uEZz4uZUOBHh0L7C2fXrVVcKyDGe5PFt/yoBfWkt3IldGxh/kFVps883EnnYp8PWFx 6Zwg==
MIME-Version: 1.0
X-Received: by 10.180.102.135 with SMTP id fo7mr21615674wib.79.1418014971783; Sun, 07 Dec 2014 21:02:51 -0800 (PST)
Received: by 10.216.78.5 with HTTP; Sun, 7 Dec 2014 21:02:51 -0800 (PST)
In-Reply-To: <54820304.9020201@gmail.com>
References: <20141205075203.54ed9ea4@echo.ms.redpill-linpro.com> <D90EED39-E226-44E2-8895-C566F133D826@steffann.nl> <54820304.9020201@gmail.com>
Date: Sun, 07 Dec 2014 21:02:51 -0800
Message-ID: <CAD6AjGRMTJKd844PUo-sDAfQmr+xuJKt8t6TDYQaCT+EGaa3xQ@mail.gmail.com>
From: Ca By <cb.list6@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary="f46d0444728fadf2660509ad56fe"
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/hmo1C2ZUnN8mGAjenAXbdELaJAQ
Cc: IPv6 Ops WG <v6ops@ietf.org>, Tore Anderson <tore@fud.no>
Subject: Re: [v6ops] New Version Notification for draft-anderson-v6ops-siit-eam-01.txt
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: <http://www.ietf.org/mail-archive/web/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: Mon, 08 Dec 2014 05:02:55 -0000

On Fri, Dec 5, 2014 at 11:09 AM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 06/12/2014 03:19, Sander Steffann wrote:
> > Hi,
> >
> >> In any case, I would like to have your "+1" on which approach you
> >> prefer of these alternatives:
> >>
> >> A) Remove all the normative RFC6145 protocol update language from
> >> draft-anderson-siit-dc, taking this document off the standards
> >> track, and have it describe the data centre use case only. Instead
> >> contain the required protocol update in a separate document dedicated
> >> to that purpose, i.e., draft-anderson-v6ops-siit-eam.
> >
> > +1
> >
> > I'd like to see the protocol stuff in a separate -eam doc and leave the
> application description in -dc. That way future work can easily reference
> the -eam work even if its use case is outside of -dc.
>
> Agreed.
>
>    Brian
>
>
+1 for moving the protocol modification work to -eam so that it will
provide a cleaner reference to any other non-data center  document.

CB


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

v2.23.0 | Report a Bug | By Email