IETF Logo Mail Archive

Re: [DMM] Second WGLC on draft-ietf-dmm-srv6-mobile-uplane

"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 01 April 2022 15:28 UTC

Return-Path: <jmh@joelhalpern.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 6C7F13A177F for <dmm@ietfa.amsl.com>; Fri, 1 Apr 2022 08:28:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.111
X-Spam-Level:
X-Spam-Status: No, score=-2.111 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, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 IFF72dmC4Iif for <dmm@ietfa.amsl.com>; Fri, 1 Apr 2022 08:28:43 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 60E293A1798 for <dmm@ietf.org>; Fri, 1 Apr 2022 08:27:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4KVPF51vKBz6GYLR; Fri, 1 Apr 2022 08:27:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1648826873; bh=ibVg2yu0XX0QGPJdrLS2yU2SvuKFN9iR4lReF1I+f38=; h=Date:Subject:To:References:From:In-Reply-To:From; b=otOyA0OpjPy5fmJSsIeMMvygQR6Qz34O0v302d43oSg4CiniWS/IfCmmbECVzKtHE R0PB/L9Ppdj9U5lqHw58ZeWPbia1s9lIxIFulGUB2+oTYverJ814js7pRVRh97L30N EyhHlcCKqYz6fgCb6kKhQLrD55SDqpXuAnKhUqmc=
X-Quarantine-ID: <1vP-VuVtkQ1A>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.21.218] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4KVPF45CpCz6G9NJ; Fri, 1 Apr 2022 08:27:51 -0700 (PDT)
Message-ID: <4d4191dc-de84-cbd5-0e8e-37df6adc65bc@joelhalpern.com>
Date: Fri, 01 Apr 2022 11:27:50 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0
Content-Language: en-US
To: "Sri Gundavelli (sgundave)" <sgundave=40cisco.com@dmarc.ietf.org>, "dmm@ietf.org" <dmm@ietf.org>
References: <100FAAE3-A63E-499C-BEDD-5074D92E2CE9@cisco.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
In-Reply-To: <100FAAE3-A63E-499C-BEDD-5074D92E2CE9@cisco.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/I7R_yA6tV2-Bc7aI0q6XPdd9vq8>
Subject: Re: [DMM] Second WGLC on draft-ietf-dmm-srv6-mobile-uplane
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: Fri, 01 Apr 2022 15:28:49 -0000

As far as I can tell, this document still attempts to redefine 3GPP 
standards in an IETF standards track document.  That is in my view 
unacceptable.

Yes, those sections are labelled "informational".  But they are still 
the same content, presented the same way.  Pretending they are 
informational in a standards track document is simply not sufficient. 
If they are really informational, pull them out to a separate 
informational document.  And we can then debate the value of publishing 
those non-standard approaches.  (Personally, I do not see the value.)

Yours,
Joel

On 4/1/2022 11:13 AM, Sri Gundavelli (sgundave) wrote:
> Folks:
> 
> We have issued a WGLC on draft-ietf-dmm-srv6-mobile-uplane in April of 
> last year. Based on the feedback and the comments from the WG, we chose 
> to hold the document so the authors can resolve the identified issues 
> from that LC. The authors have worked with the reviewers and have 
> revised the document. They believe that there are no open issues. We are 
> issuing a second last call. This message commences a one-week WGLC for 
> all feedback.  Please provide any additional feedback you may have.
> 
> https://datatracker.ietf.org/doc/html/draft-ietf-dmm-srv6-mobile-uplane-19 
> <https://datatracker.ietf.org/doc/html/draft-ietf-dmm-srv6-mobile-uplane-19>
> 
> Sri
> 
> Chair DMM WG
> 
> *From: *Sri Gundavelli <sgundave@cisco.com>
> *Date: *Wednesday, April 7, 2021 at 10:35 AM
> *To: *"dmm@ietf.org" <dmm@ietf.org>
> *Subject: *WGLC on draft-ietf-dmm-srv6-mobile-uplane-11
> 
> Working Group:
> 
> As we discussed in the last IETF meeting, we are issuingWGLCon 
> draft-ietf-dmm-srv6-mobile-uplane-11.
> 
> The document went through several revisions and there were good amount 
> of reviews on this document. I am very pleased with the quality of this 
> document. The authors have addressed all the comments and there are no 
> open issues that we are tracking at this time. We believe the document 
> is ready for IESG reviews and like to confirm the same from the working 
> group.
> 
> The following message commences a two weekWGLCfor all feedback.
> 
> Document Link:
> 
> https://www.ietf.org/archive/id/draft-ietf-dmm-srv6-mobile-uplane-11.txt 
> <https://www.ietf.org/archive/id/draft-ietf-dmm-srv6-mobile-uplane-11.txt>
> 
> Please post any comments/concerns on this document.
> 
> Thanks!
> 
> Sri
> 
> 
> _______________________________________________
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm

v2.23.0 | Report a Bug | By Email