IETF Logo Mail Archive

Re: [bcause] Inter SDO relationship considerations

Greg Mirsky <gregimirsky@gmail.com> Fri, 29 March 2019 10:33 UTC

Return-Path: <gregimirsky@gmail.com>
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 953BB12025F for <bcause@ietfa.amsl.com>; Fri, 29 Mar 2019 03:33:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.com
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 VGNLp_a7J2YA for <bcause@ietfa.amsl.com>; Fri, 29 Mar 2019 03:33:25 -0700 (PDT)
Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8205812025E for <bcause@ietf.org>; Fri, 29 Mar 2019 03:33:25 -0700 (PDT)
Received: by mail-lj1-x230.google.com with SMTP id t4so1492589ljc.2 for <bcause@ietf.org>; Fri, 29 Mar 2019 03:33:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6ggy8fBCVNhCXBULBF2VpwoX/JbegKE6HBsUHu6QTHo=; b=enmmzJHNjgluhZHQ0qkVdPJF6vuxWcYkmBWlgQf65Nl8gZJd6MZ7iidifnlBmGoTNT amBKOAWY7DfHpJxpQ5opP6Lat9Q6odos/RR39UL5Z+EDp93s4VdpR+c19Mwz/P7cVPaO jFTbtVr9l1U/6y26dV56dA602DqS8NNCOKsNWhRB5yj8A9s9QsL2SpY4FelQyoS0kjjD Ob742hfKJNagTW9pzJS53cS7TWk54JavxRMwLV4mly2+96KOA1aJum1BxHfVHFl72LEJ BO5GRRuAaEgtHSyfflaS/LxUWzgu09BwPz5DU+2dPHY0U7O4ebI9Yn2qF6BiEytcM5pc LeSw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6ggy8fBCVNhCXBULBF2VpwoX/JbegKE6HBsUHu6QTHo=; b=M5j5oZ8MmvLG2UtbZQIUxAWX/sdz9OPaKqWzAN0PKbyLgmVy0BfjR3Sk7skJK37DVJ xVTZHtuvcBIc6dRQoolWU884m+Pau1SmNdnc2/c4JvCMZaHejcFKFqqn51Vjn1WfX5/p USwelm52Z63+x1VSSnyiSAZO/JNNqI9Y+AB3//W4WLqQVKNlKxKPkf0I2QbbgBec4N0J WzmguhUlJVjcbIyoDHeVdi1Tui+3CFAAqpA1D1SOwNprdiN7qvamW+3bVFmQkA0lYmAS Mj80fltsnkIpuXq0hg15qwGxwG9y/y/tzkhRr9LTpHLDIGa7+UeOBfylojUGRuoAbRr4 y5fw==
X-Gm-Message-State: APjAAAXdeY+iH/RbmmhW+cZq54OM/WtnKCpcOf0kyBnG84NJ2sk9T3+9 lxmYP+LiM48WT+7ob7/oTgyJ+49OX2I/nE/xPyc=
X-Google-Smtp-Source: APXvYqwPEoEUms95/3U9iMBAsvKYgUunpM1pP4E70Ng2Ecv/N/aUCMr7PlGKIufJ2oW09PILCi42mVtTD5GigJvcsI0=
X-Received: by 2002:a2e:910b:: with SMTP id m11mr4582693ljg.14.1553855603599; Fri, 29 Mar 2019 03:33:23 -0700 (PDT)
MIME-Version: 1.0
References: <2D09D61DDFA73D4C884805CC7865E6114E11FA36@GAALPA1MSGUSRBF.ITServices.sbc.com> <987A987E-1667-424D-BAC8-7DF518E32735@ericsson.com>
In-Reply-To: <987A987E-1667-424D-BAC8-7DF518E32735@ericsson.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Fri, 29 Mar 2019 11:33:13 +0100
Message-ID: <CA+RyBmXuJx0TM9o_RNvcUd+cvdQmE+TySDS156jcc0QcAiA0Yw@mail.gmail.com>
To: David Sinicrope <david.sinicrope@ericsson.com>
Cc: "bcause@ietf.org" <bcause@ietf.org>, "trammell@tik.ee.ethz.ch" <trammell@tik.ee.ethz.ch>
Content-Type: multipart/alternative; boundary="00000000000048ee7805853933ae"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bcause/HR6gETyPgggNJmVJsxOz6FxZ79E>
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 10:33:29 -0000

Hi David,
I think that the comment that brought your attention is one of the
individual opinions that not necessarily reflect the opinion of CUSP
supporters.

Regards,
Greg

On Fri, Mar 29, 2019 at 10:40 AM David Sinicrope <
david.sinicrope@ericsson.com> wrote:

> (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
> https://www.ietf.org/mailman/listinfo/bcause
>

v2.23.0 | Report a Bug | By Email