IETF Logo Mail Archive

Re: [bcause] Inter SDO relationship considerations

Gregory Dalle <gdalle@juniper.net> Fri, 29 March 2019 11:22 UTC

Return-Path: <gdalle@juniper.net>
X-Original-To: bcause@ietfa.amsl.com
Delivered-To: bcause@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E14A2120271 for <bcause@ietfa.amsl.com>; Fri, 29 Mar 2019 04:22:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, KHOP_DYNAMIC=0.85, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 1U4_C9uJyRsx for <bcause@ietfa.amsl.com>; Fri, 29 Mar 2019 04:22:44 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 0031D120267 for <bcause@ietf.org>; Fri, 29 Mar 2019 04:22:43 -0700 (PDT)
Received: from pps.filterd (m0108162.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x2TBEOZm017133; Fri, 29 Mar 2019 04:22:36 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=JtxB3GDq7kKwOKlEdIMIk6btLMPiHy8pkxIda8omhrw=; b=BSsmlJx1ZrGr88efy91DCx7ejoMb/5G6Q7bGXui/rh7+caQszwmfbs03YfBtHNlR3E+Y ib0kgGw2tXRY8DPSrM1a+yQ6qVRp8hS6dmhZLQG4D+xvT99Jfp333xbjBaD8og1B3XtU exaBqhsznLINjU/rBk5FIYYff7QELgPtBCU466DNn60nV4Y6iqE0/wkOtXOHbwOrE6cM u7Beti97FxQfOaXu1+HA4VFGiyBf83pQHo6weLFxkfpChB2JsA9O9eQpQJf8vBvYBnjQ +e5y9OmjiUwTTnoALTiAsh2WzRcMXTIsgsToRl0lb0v09oT53z4uDJDI4VeAJmyMg0r1 Pg==
Received: from nam04-co1-obe.outbound.protection.outlook.com (mail-co1nam04lp2059.outbound.protection.outlook.com [104.47.45.59]) by mx0b-00273201.pphosted.com with ESMTP id 2rhemrgccd-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 29 Mar 2019 04:22:36 -0700
Received: from MWHPR05MB3360.namprd05.prod.outlook.com (10.174.175.145) by MWHPR05MB2879.namprd05.prod.outlook.com (10.168.245.137) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1771.8; Fri, 29 Mar 2019 11:22:33 +0000
Received: from MWHPR05MB3360.namprd05.prod.outlook.com ([fe80::9895:5636:5403:b39d]) by MWHPR05MB3360.namprd05.prod.outlook.com ([fe80::9895:5636:5403:b39d%4]) with mapi id 15.20.1771.006; Fri, 29 Mar 2019 11:22:33 +0000
From: Gregory Dalle <gdalle@juniper.net>
To: Mach Chen <mach.chen@huawei.com>
CC: David Sinicrope <david.sinicrope@ericsson.com>, "bcause@ietf.org" <bcause@ietf.org>, "trammell@tik.ee.ethz.ch" <trammell@tik.ee.ethz.ch>
Thread-Topic: [bcause] Inter SDO relationship considerations
Thread-Index: AQHU5hNlwNsTm5pFFU6Uujiowsy9ZKYiYr4AgAAUg/8=
Date: Fri, 29 Mar 2019 11:22:33 +0000
Message-ID: <1E3BA1F7-39B2-40CE-8129-32891959AE77@juniper.net>
References: <2D09D61DDFA73D4C884805CC7865E6114E11FA36@GAALPA1MSGUSRBF.ITServices.sbc.com> 0484FBCE-34ED-432A-90F9-A054D9412F85, <987A987E-1667-424D-BAC8-7DF518E32735@ericsson.com>, 1DBED2D7-4A4C-4549-8EAC-C2C7A29EDA88
In-Reply-To: 1DBED2D7-4A4C-4549-8EAC-C2C7A29EDA88
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2601:182:cd00:2829:92f:55:8087:e649]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: a124b527-6d0b-4937-117d-08d6b438d6d5
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(4618075)(2017052603328)(7153060)(7193020); SRVR:MWHPR05MB2879;
x-ms-traffictypediagnostic: MWHPR05MB2879:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <MWHPR05MB2879D3137D45D4D1255E2C0DD35A0@MWHPR05MB2879.namprd05.prod.outlook.com>
x-forefront-prvs: 0991CAB7B3
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(396003)(366004)(39860400002)(346002)(136003)(189003)(199004)(25786009)(316002)(14454004)(6246003)(6116002)(33656002)(53936002)(54906003)(478600001)(99286004)(966005)(6512007)(236005)(5660300002)(97736004)(105586002)(68736007)(36756003)(106356001)(6306002)(54896002)(82746002)(8676002)(8936002)(81166006)(606006)(81156014)(7736002)(46003)(6486002)(2616005)(476003)(229853002)(486006)(6506007)(83716004)(71190400001)(71200400001)(6436002)(2906002)(102836004)(4326008)(256004)(86362001)(53546011)(76176011)(6916009)(11346002)(186003)(446003); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR05MB2879; H:MWHPR05MB3360.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: UIUG8eNijNl4aNSieMuSdAe+n+ny/NjDsR6rpm+L757gkpxVaq8TdHfo14qVUfotC4inos3fNtDfTMbhoj4mNH9aTE3i0FoA60KUrVCj8upLfkG2+iQdLrUqqDZ1Hu+DGsp/c114sdipCj3CI4S7XtH1x+iuEpV6cS128mXoH30lD3TChS8zeo8CPyuoVxigblnnNxQAnRt5j5TfT9D9/gqWY5Cw3S4WhFs4T6+Afn83T/v9bC063sfdE7VMRdY1KfnUAubcgLgCEzLTPRw2IYZk4R4IyAxp3LKnOrlI7diGkBux8ENuPkPr6+KQfFTBT6F1dWNv0nR0Nsst3UmAUTKcAKDH4wsXoLCG6Aagge42b36VcEhjvObutxFiSbZ+iv9IFyC7yKxMtOaF6WnDlX7loBKOIV3OHlZScFAUco4=
Content-Type: multipart/alternative; boundary="_000_1E3BA1F739B240CE812932891959AE77junipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: a124b527-6d0b-4937-117d-08d6b438d6d5
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Mar 2019 11:22:33.3849 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR05MB2879
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-29_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1903290082
Archived-At: <https://mailarchive.ietf.org/arch/msg/bcause/zfh5av75HrkbBhkPN2EiYcBkJNE>
Subject: Re: [bcause] Inter SDO relationship considerations
X-BeenThere: bcause@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <bcause.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bcause>, <mailto:bcause-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bcause/>
List-Post: <mailto:bcause@ietf.org>
List-Help: <mailto:bcause-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bcause>, <mailto:bcause-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Mar 2019 11:22:47 -0000

Mach, it would overlap. BBF is addressing CUPS both for BNG (WT-459) and CUPS for FMC (WT-458), as described in liaisons.

Greg

On Mar 29, 2019, at 6:09 AM, Mach Chen <mach.chen@huawei.com<mailto:mach.chen@huawei.com>> wrote:

I think your statement is not true, there is no overlap
. As one of the proponents, I am sure that the CUSP is only targeting to address CMCC's fixed BNG CUPS  requirements.

Best regards,
Mach
发件人：David Sinicrope <david.sinicrope@ericsson.com<mailto:david.sinicrope@ericsson.com>>
收件人：bcause@ietf.org<mailto:bcause@ietf.org> <bcause@ietf.org<mailto:bcause@ietf.org>>
抄 送：trammell@tik.ee.ethz.ch<mailto:trammell@tik.ee.ethz.ch> <trammell@tik.ee.ethz.ch<mailto:trammell@tik.ee.ethz.ch>>
时间：2019-03-29 10:40:16
主 题：[bcause] Inter SDO relationship considerations

(IETF Liaison Manager to BBF hat on)

The statements on this list, especially those to the effect that CUSP work in the IETF would not exclude FMC, indicate that there is high potential (and intent?) that both the BBF and the IETF would be working on two competing solutions, i.e., two different solutions competing for the same problem.

The two organizations pursuing competing solutions creates an inherent strain on the inter SDO relationship, that to this point has been coordinated, cooperative and cordial.

Further, given the indications in the liaisons from BBF that they intend to work cooperatively with 3GPP, should they decide to pursue PFCP as a solution, would then potentially put IETF in competition with 3GPP as well.

Introducing this inter-SDO strain has potential impacts beyond this immediate bcause issue to other work between the organizations.

I would ask the participants and ADs to please consider these potential issues in your deliberations.

Thank-you,
Dave

--
bcause mailing list
bcause@ietf.org<mailto:bcause@ietf.org>
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_bcause&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=VhX0NAIO1d7yQxdURKFPY59GAxttnQcfkn45tfRnREs&m=JC3Qb6i8mCuJ1qoJ8V-GimcEg54-mMyrB33kAH77u5s&s=rParcq-0T3mErgJ0LkEVsN2Re1I49f7UqUi1l9dvxnU&e=

v2.23.0 | Report a Bug | By Email