Re: [Status] SPRING Charter

Stewart Bryant <stbryant@cisco.com> Wed, 16 October 2013 17:20 UTC

Return-Path: <stbryant@cisco.com>
X-Original-To: status@ietfa.amsl.com
Delivered-To: status@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BD6611E8182; Wed, 16 Oct 2013 10:20:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.524
X-Spam-Level:
X-Spam-Status: No, score=-110.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 ODJHvXZtNZhq; Wed, 16 Oct 2013 10:19:59 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 8450411E8118; Wed, 16 Oct 2013 10:19:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1367; q=dns/txt; s=iport; t=1381943995; x=1383153595; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=PV/vNaWGuN0yF1Ggc0BWMV0C0cC+ltcTJheaPwsWe1Q=; b=fGlKwRjHkvCN24z+8bpl400iER9C/Lk46c3MYcuVVc6jA3+8dYPis2BV LTWTj2GZ6vqiRWfDV3ZflRJYKwCJFzOiecPuhxO08Sk0AZY2aHps+9fXp tVgqiO/EIBAInFhXV6Me6P+yIEDJl3nonexgQ+PHcC06P/WvhlP5et4gv k=;
X-IronPort-AV: E=Sophos;i="4.93,508,1378857600"; d="scan'208";a="18322033"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-3.cisco.com with ESMTP; 16 Oct 2013 17:19:54 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r9GHJmCJ007723 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Oct 2013 17:19:50 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r9GHJksh026109; Wed, 16 Oct 2013 18:19:47 +0100 (BST)
Message-ID: <525ECAB2.6030302@cisco.com>
Date: Wed, 16 Oct 2013 18:19:46 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, Thomas Narten <narten@us.ibm.com>
References: <BBD66FD99311804F80324E8139B3C94E39641304@xmb-aln-x15.cisco.com>
In-Reply-To: <BBD66FD99311804F80324E8139B3C94E39641304@xmb-aln-x15.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "status@ietf.org" <status@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [Status] SPRING Charter
X-BeenThere: status@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <status.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/status>, <mailto:status-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/status>
List-Post: <mailto:status@ietf.org>
List-Help: <mailto:status-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/status>, <mailto:status-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Oct 2013 17:20:05 -0000

On 16/10/2013 13:47, Alvaro Retana (aretana) wrote:
> On 10/15/13 3:46 PM, "Thomas Narten" <narten@us.ibm.com> wrote:
>
> Thomas:
>
> Hi!
>
>> Also, this item:
>>
>>>   Definition of requirements and/or any new data plane
>>>     encodings and procedures, required to implement
>>>     the use cases. Such procedures must include the
>>>     necessary security considerations.
>> Suggests to me that SPRING is being given the go ahead to define IPv6
>> mechanisms to do SR. IMO, any IPv6 protocol work should be done in
>> 6MAN. SPRING should do requirements, etc., but IMO IPv6 protocol work
>> needs to be done where the IPv6 expertise is. Or at the very least
>> with very close coordination.
> The charter also reads:
>
> "Any modification of or extension to existing architectures,
> data planes, or control or management plane protocols
> must be carried out in the working groups responsible
> for the architecture, data plane, or control or
> management plane protocol being modified and in
> co-ordination with this working group, but may be
> done in this working group after agreement with
> all the relevant WG chairs and responsible Area Directors."
>
> So I think we're in agreement.
>
Yes, but it looks like the deliverables text is slight out of
alignment - hence my proposed slight tweek

s/and\/or/for/

Stewart