IETF Logo Mail Archive

Re: [L2sm] Proposed Liaison to 3GPP SA5

"Adrian Farrel" <adrian@olddog.co.uk> Tue, 05 June 2018 20:36 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: l2sm@ietfa.amsl.com
Delivered-To: l2sm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8C53131165 for <l2sm@ietfa.amsl.com>; Tue, 5 Jun 2018 13:36:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=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 QfeXTFO5ozJ0 for <l2sm@ietfa.amsl.com>; Tue, 5 Jun 2018 13:36:12 -0700 (PDT)
Received: from mta8.iomartmail.com (mta8.iomartmail.com [62.128.193.158]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D4FA130DE5 for <l2sm@ietf.org>; Tue, 5 Jun 2018 13:36:12 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id w55Ka7fb012000; Tue, 5 Jun 2018 21:36:07 +0100
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 0E1A62203B; Tue, 5 Jun 2018 21:36:07 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs1.iomartmail.com (Postfix) with ESMTPS id ED7E32203A; Tue, 5 Jun 2018 21:36:06 +0100 (BST)
Received: from 950129200 (243.125.113.87.dyn.plus.net [87.113.125.243]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id w55Ka4HV015206 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Jun 2018 21:36:05 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: "'Roque Gagliano (rogaglia)'" <rogaglia@cisco.com>
Cc: l2sm@ietf.org
References: <000901d3fbf5$5648d790$02da86b0$@olddog.co.uk> <7ee2d1342bf6403583d834a1ae3f2d7d@TELMBXB02RM001.telecomitalia.local> <01a901d3fce6$00486b20$00d94160$@olddog.co.uk> <2717B04F-A52D-4F07-BCD6-54672978429E@cisco.com> <01c401d3fcf3$c389b230$4a9d1690$@olddog.co.uk> <D14DDD23-258C-4839-9CF8-4A9E989878F9@cisco.com> <01c901d3fcfd$856d13c0$90473b40$@olddog.co.uk> <40C646D5-7AE8-4715-9527-F6F75461ABD1@cisco.com>
In-Reply-To: <40C646D5-7AE8-4715-9527-F6F75461ABD1@cisco.com>
Date: Tue, 05 Jun 2018 21:36:00 +0100
Message-ID: <01df01d3fd0c$d19cdeb0$74d69c10$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIOf7qJKx24xl1w/pQ68zsvGbGRtQGs1yWjAcptn+ICAJuhNwG6lm/OAV6uH4sCHFBz5AHIXsF2o3ln+BA=
Content-Language: en-gb
X-Originating-IP: 87.113.125.243
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-23890.002
X-TM-AS-Result: No--2.114-10.0-31-10
X-imss-scan-details: No--2.114-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-23890.002
X-TMASE-Result: 10--2.113800-10.000000
X-TMASE-MatchedRID: +c13yJDs9004HKI/yaqRm5gGnz93PV931kqyrcMalqUhvFjBsLEZNKEs hzqhV9N+O5OUpE6rya5+hDiODe0ZMOM2fQ6STlVfcFEiuPxHjsW36GGfwjLoZQzvg1/q1MH255o ZBbl7bK/LKYztBLtB9YbXzhjksitpv1l2Uvx6idqWlioo2ZbGwdmzcdRxL+xwKrauXd3MZDVH1m HLcbEpxcayjCYvPE+jw6T2mFMuHhBPzGiBCIj49pRnB/zWyw9pZL9Lz4e5zSpXKGRjbfPggnRFl Vqj/v6XOWMttz6Ud2L20urTRrvzyKfItuohgjfnw/3NmPJsa4pNWfnUnboML1TXUX0dTQdP
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/-T8vjoIR_P0jvUCMED_CVccJS6I>
Subject: Re: [L2sm] Proposed Liaison to 3GPP SA5
X-BeenThere: l2sm@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" <l2sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2sm>, <mailto:l2sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l2sm/>
List-Post: <mailto:l2sm@ietf.org>
List-Help: <mailto:l2sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2sm>, <mailto:l2sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jun 2018 20:36:15 -0000

> Independently if RFC 8309 was approved following the correct process (which I
> believe is your latest point), we cannot refer to it as the IETF community
> consensual opinion on how service models should be interpreted as it was
> expressed in your original statement but just a recompilation of possible
> examples.

OK, I'm talking as a co-author of 8309, and not as L2SM co-chair. 

Why cannot we refer to it as the IETF community consensual opinion? Or is your point that I am misrepresenting the content of the document?

Cheers,
Adrian

> Please consider my contribution for a modified text:
> "RFC 8199 and RFC 8309 are informational documents developed by the IETF
> community to show examples on how service models could be implemented."

v2.23.0 | Report a Bug | By Email