Re: [DMM] New Version Notification for draft-clt-dmm-tn-aware-mobility-07.txt

Uma Chunduri <umac.ietf@gmail.com> Thu, 22 October 2020 01:18 UTC

Return-Path: <umac.ietf@gmail.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C74A3A0BCF for <dmm@ietfa.amsl.com>; Wed, 21 Oct 2020 18:18:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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 3q60jzdtDjvL for <dmm@ietfa.amsl.com>; Wed, 21 Oct 2020 18:18:22 -0700 (PDT)
Received: from mail-vs1-xe2a.google.com (mail-vs1-xe2a.google.com [IPv6:2607:f8b0:4864:20::e2a]) (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 BB3433A0C32 for <dmm@ietf.org>; Wed, 21 Oct 2020 18:18:22 -0700 (PDT)
Received: by mail-vs1-xe2a.google.com with SMTP id h5so2087449vsp.3 for <dmm@ietf.org>; Wed, 21 Oct 2020 18:18:22 -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; bh=2BPPrcBNAWAcPi2/0YuIyr5qakT7AjafucXpni/EqCk=; b=XOZ7tcA6SAT98IFH69M9kxC5mnexmXkUN+z7xy+ox+6Q0yhz3fPlm59I1BMyZvQB8Z /q+iuj640I8Vtv7tJjqDvkJRQpBFN7afh2SAG7qR81ExugwEYxhBXDXF520b49aO87zA N2usFDd64DJav+pwxXUOIZfp6T7mU3RHFidmQ853AgU7pI9Xv3vyQjcoER9hN/oOxANl B9Q8F8h8TFbLxysmPQ540suv9gKFzXL0cl9TAWeAsfPZAtkCdgcZtqXlydzzq9fJbMpz Q3d/gvJmrTwCSG3EIr21Njg5+NEV4+6jqGFpgwTX+t82hwXV7l/jTspmnIH2jO+KZYAw Sd8w==
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; bh=2BPPrcBNAWAcPi2/0YuIyr5qakT7AjafucXpni/EqCk=; b=pEmJxgmBhGX2fHg8VewyVpNlbMYtyE9VXLErTBI5aEabiWSWy6wDrpnSHTbeXeFQEr UXejj28srOxqNO4a3QDlbb3NmVfh1Sk5BeCniPrGUTRh5isGNnvh0grm6svCoQMdmwK4 U8OYN0ehxxc3Ghw1hQg8oHENw4pNftDTsa6ZTzsnSii4lXFM+xq9w9oSmFMy7HcDlcji 0LuOmXCG4f39gnj4MubI0uJtoZRBsxK24LDSCDKLEnd234Iijco3ROOTp1qixBW/7pfS eIGthdp/UVEBEhZbLa1tazt/pn5p+cCtskpl/gU3Js+QsLlkZGCRNYnEzDDgmEHVYdkx 5xww==
X-Gm-Message-State: AOAM533e51m56Ievn9l1hKLGJTiGY+YFLu+jjexokbFebTI8h27SQ/Oq Z9NLl5y2MXTvUQ+WSXL2/Qy4N14sGuPrTkp4IxWFQ3V6Hbw=
X-Google-Smtp-Source: ABdhPJxs1HTUqnXpYmBIWm3KSZp8QyQyCdq6q5sdgzen/FIZh3udTycYJR6rjfeK525ALDM3acdlAxWldDznDeIK5uE=
X-Received: by 2002:a67:2883:: with SMTP id o125mr179110vso.46.1603329501387; Wed, 21 Oct 2020 18:18:21 -0700 (PDT)
MIME-Version: 1.0
References: <160133669315.20579.1349579162555966845@ietfa.amsl.com> <CAF18ct6U17CJ2_ijgKES2Rd9CqgxzwBAectqH6EhNtXUyA83ng@mail.gmail.com> <34BB0DFC-FACD-4D09-A4E1-791E41B25748@cisco.com> <BY5PR14MB41453099EB0C7E637CA411C4FA1C0@BY5PR14MB4145.namprd14.prod.outlook.com>
In-Reply-To: <BY5PR14MB41453099EB0C7E637CA411C4FA1C0@BY5PR14MB4145.namprd14.prod.outlook.com>
From: Uma Chunduri <umac.ietf@gmail.com>
Date: Wed, 21 Oct 2020 18:18:22 -0700
Message-ID: <CAF18ct5T3_6PFKPRCa=+gEUSqYeJEOKQPz-MEYYfg5ZzExZRog@mail.gmail.com>
To: dmm <dmm@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000635fa405b2383dc9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/fCWxyM0_m82FSGN8X1HgBnmXino>
Subject: Re: [DMM] New Version Notification for draft-clt-dmm-tn-aware-mobility-07.txt
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2020 01:18:24 -0000

Thanks Kaushik for your comments. Need a quick clarification (see below ..)

On Wed, Oct 21, 2020 at 1:29 PM Majumdar, Kausik <
Kausik.Majumdar@commscope.com> wrote:

> Hi Uma et all,
>
>
>
> Thanks for putting together this draft to describe the framework for
> mapping the slices in 5G mobile systems to transport slices in IP towards
> the UPF. This framework is valuable and we are actually looking for further
> extensions of the TN characteristics in non-mobility domain (SD-WAN) and
> that is being worked out to be submitted in RTG WG.
>

Thanks.


>
>
> I would also request you to consider the Security Characteristics in
> addition to the current Transport Path characteristics. Preserving the
> security characteristics in non-mobility SD-WAN domain would be an
> important aspects. My suggestions would be to extend the current SST for
> secure traffic. As a result, it would be good if we can define additional
> UDP Source Port range to capture the Security characteristics for the
> current service types.
>

We already described the generic case where security is applied (section
2.6), when the user plane emits the packet to transport (could be N3/N9
interfaces or S1U interface terminating at SGWs).
That addresses mostly shared transport cases.
If I understand correctly, you want security done by PE's before gNB/UPF??
I can imagine few usef of this but can you explain why you are looking for
this option?


>
>
> I would be happy to share more context on the use cases and discuss
> further on the approaches.
>

Sure. But is this a mandatory option for your E2E use case with
SD-WAN beyond mobility domain?

--
Uma C.


>
>
> Regards,
>
> Kausik
>
>
>
>