IETF Logo Mail Archive

Re: [Status] SPRING Charter

"Alvaro Retana (aretana)" <aretana@cisco.com> Wed, 16 October 2013 12:48 UTC

Return-Path: <aretana@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 C173A11E81D6; Wed, 16 Oct 2013 05:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 9cAcJlyHJKeJ; Wed, 16 Oct 2013 05:47:57 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 6433411E81D1; Wed, 16 Oct 2013 05:47:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1150; q=dns/txt; s=iport; t=1381927673; x=1383137273; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=qIz9jFz/ivoTacW3qZPv+0bt0FzlNHJyvvxH4dbfCFI=; b=VvlRZhoGV/6Kcs60B3VMBtpofSu42HDX3GjHpSnYSOpAA+knokXi7/0C NM0s0tCI5W0wRNmZuXdm1/CjJP02fbKuncJr2ggffKdZnzSWWayKvfA5m Xfgp6+8V9E0zTp5p5YRlc+ZEGHJ1mh43ZvKoUtP9MtiP4s2pLMQvmZ+XK U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFAJmKXlKtJV2Z/2dsb2JhbABagweBCsIPgR0WdIInAQQ6LQQOEgEIEhAUQhcOAgQOBQiHfr8GjyAxB4MfgQYDqgaDJIIp
X-IronPort-AV: E=Sophos;i="4.93,507,1378857600"; d="scan'208";a="269754124"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-9.cisco.com with ESMTP; 16 Oct 2013 12:47:46 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r9GClkQC015012 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 16 Oct 2013 12:47:46 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.40]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0318.004; Wed, 16 Oct 2013 07:47:46 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: Thomas Narten <narten@us.ibm.com>
Thread-Topic: [Status] SPRING Charter
Thread-Index: AQHOxrVkUYi6pW/k1kW1dQ64aj+T65n2IEsAgAGjcwA=
Date: Wed, 16 Oct 2013 12:47:45 +0000
Message-ID: <BBD66FD99311804F80324E8139B3C94E39641304@xmb-aln-x15.cisco.com>
In-Reply-To: <201310151346.r9FDkSIl023262@cichlid.raleigh.ibm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.82.209.13]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <669F048E8735444F9C29CFE65E6AFFFE@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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
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 12:48:02 -0000

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.

Thanks!

Alvaro.

v2.23.0 | Report a Bug | By Email