Re: [bcause] PFCP not equal to FMC, Why not choose PFCP

Richard Patterson <richard@helix.net.nz> Sat, 30 March 2019 00:05 UTC

Return-Path: <richard@helix.net.nz>
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 63181120282 for <bcause@ietfa.amsl.com>; Fri, 29 Mar 2019 17:05:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=helix-net-nz.20150623.gappssmtp.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 ra3xuxJDiTzp for <bcause@ietfa.amsl.com>; Fri, 29 Mar 2019 17:05:40 -0700 (PDT)
Received: from mail-yw1-xc2f.google.com (mail-yw1-xc2f.google.com [IPv6:2607:f8b0:4864:20::c2f]) (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 C91D5120059 for <bcause@ietf.org>; Fri, 29 Mar 2019 17:05:39 -0700 (PDT)
Received: by mail-yw1-xc2f.google.com with SMTP id l5so1311353ywa.0 for <bcause@ietf.org>; Fri, 29 Mar 2019 17:05:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=helix-net-nz.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=EhIzlJElJgTAkDrnUOLHpdZia4GGON/LE81kJAM7gt4=; b=rwEri+hqFfy3LNzmZ+YQmzrNWtxwYLIe7N8OTjPZvI19ks2wA2LZARpvu97iMa4HJr 2CbncmKk1v7pRE2JbnShzorSB6hUL/GAUFd18riPERfQLuLPmrFWa3rkVPi4Q7OtwZC2 If3X+El/P/ybZeZO/Ho3ix1CWQLLG80WFlLfCQpev3lsqBE+0hguLMU1UmzOYdjQlgjn THnStaHogG5Z8xv8m3/fluNcDU69WVzN/nSQXXtzwmNa0qCOMYnDFvAHvj9jkkiPRhFr woV+zIgxoMmZmktQLE95AYGSYYtWCLW/gfnYO9ZDmvihvdhrgfzgfpahqoehVFkMUvUB BaYg==
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=EhIzlJElJgTAkDrnUOLHpdZia4GGON/LE81kJAM7gt4=; b=SlfKU8BZTbcz8RW2/eprsVxRNpHGruzgK7Ofr59h+XDdktF4yY5fJ3V3NCu0RStQGO ry8dFb8D+OxQ/AKQeTEfkPFZwh5ZPyTX2wPGC2h6qaDuUd8379S77yRtkmgVPUjGxLpS bqM+G5FoiliduhSy3CPKa6ou8ClhWX2pkoID71X8r9pTFMfvA1NuP+Hw227RFzd5p1pJ CDSWz9nOcoAGIItHEe8YcrJo0OIa/L0qSAaFtyGVTOZ476+tJgn2nBLXrKFIBZySe8fL 6dXA4iXmLlzt5xJVhG3T+9WjJFC6su67zNiwKSGWh89t8zMLhhFBoxjC1JIDC1l7lmDn /KQA==
X-Gm-Message-State: APjAAAUasDRyVxowZfFECZi4FXngtyG5ojnN5+iG+s7aSsvFLxJIu446 OojuXJ3BOxce2bBllXYeDU9nqx1BNhY=
X-Google-Smtp-Source: APXvYqzK0r2CAgne+SJVrA/wt1Y6pRF3DP/XmUYbQMwgr/zDxCTUWaxN4s/5ZOBFN/5Hvhha/t7adg==
X-Received: by 2002:a81:2511:: with SMTP id l17mr44787344ywl.288.1553904338831; Fri, 29 Mar 2019 17:05:38 -0700 (PDT)
Received: from mail-yb1-f177.google.com (mail-yb1-f177.google.com. [209.85.219.177]) by smtp.gmail.com with ESMTPSA id g1sm1379269ywf.0.2019.03.29.17.05.37 for <bcause@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 29 Mar 2019 17:05:37 -0700 (PDT)
Received: by mail-yb1-f177.google.com with SMTP id u75so1498017ybi.4 for <bcause@ietf.org>; Fri, 29 Mar 2019 17:05:37 -0700 (PDT)
X-Received: by 2002:a25:4158:: with SMTP id o85mr41571705yba.205.1553904337283; Fri, 29 Mar 2019 17:05:37 -0700 (PDT)
MIME-Version: 1.0
References: <BN6PR22MB0771AD2F5A785C1B08318D8B87580@BN6PR22MB0771.namprd22.prod.outlook.com> <F14D3C24A54A484FB585F96F625D2D991E528046@dggeml509-mbx.china.huawei.com>
In-Reply-To: <F14D3C24A54A484FB585F96F625D2D991E528046@dggeml509-mbx.china.huawei.com>
From: Richard Patterson <richard@helix.net.nz>
Date: Sat, 30 Mar 2019 01:05:19 +0100
X-Gmail-Original-Message-ID: <CAHL_VyBjcomyhKvjW8EB01m3QSifKfonhZCux9vx=OCH30fr+g@mail.gmail.com>
Message-ID: <CAHL_VyBjcomyhKvjW8EB01m3QSifKfonhZCux9vx=OCH30fr+g@mail.gmail.com>
To: "Songjun (Network)" <song.jun@huawei.com>
Cc: "bcause@ietf.org" <bcause@ietf.org>
Content-Type: multipart/related; boundary="0000000000000ad0730585448cfa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bcause/qYojGTrgB-Nt7VsDLlLqSlEzmOg>
Subject: Re: [bcause] PFCP not equal to FMC, Why not choose PFCP
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: Sat, 30 Mar 2019 00:05:43 -0000

Hi Song Jun,

Thanks for your detailed email.

I think a lot of people will have queries around this particular statement
of yours regarding PFCP:
ü  We found that nearly all requirements of BNG were needed to extended in
current protocol. That seems to rewrite a new protocol.

Could you please elaborate on this statement?   Where do you see that PFCP
is deficient for fixed line BNG?
If you've got detailed analysis of this, this would be great to see
publicly. From what I've heard, PFCP is easily extendable to satisfy the
requirements for fixed-line BNG.

You also make the assertion:  ü  IETF is the right place to define a
protocol for BNG, 3GPP is the right place to extend PFCP.
There is precedent already for the BBF extending protocols such as DHCP and
PPPoE with various options.   I think we need to properly understand the
extent of how PFCP needs to be extended, in order to decide where best to
make the extension, or if we should just build a new protocol.   I do
however agree that if it's more than a small extension required, then
perhaps the IETF should start from scratch, but I don't see this right now.

-Richard