Re: [sipcore] Activity proposal on: New Version Notification for draft-jesske-update-p-visited-network-03.txt
Brian Rosen <br@brianrosen.net> Fri, 31 March 2023 08:45 UTC
Return-Path: <br@brianrosen.net>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A42FC14CF1A for <sipcore@ietfa.amsl.com>; Fri, 31 Mar 2023 01:45:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.085
X-Spam-Level:
X-Spam-Status: No, score=-2.085 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=brianrosen.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y6N1V8YsUfTH for <sipcore@ietfa.amsl.com>; Fri, 31 Mar 2023 01:45:25 -0700 (PDT)
Received: from mail-qv1-xf29.google.com (mail-qv1-xf29.google.com [IPv6:2607:f8b0:4864:20::f29]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 8FBA1C14F747 for <sipcore@ietf.org>; Fri, 31 Mar 2023 01:45:25 -0700 (PDT)
Received: by mail-qv1-xf29.google.com with SMTP id oe8so15910739qvb.6 for <sipcore@ietf.org>; Fri, 31 Mar 2023 01:45:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen.net; s=google; t=1680252324; x=1682844324; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=9R0pmSOXEmoWLF3xHrqKFR0ZIX1xVJ9vEp3dmqdHEPA=; b=SamURziAYHigs3vJeemMSSChMGwi7qk/yV1ZJBKmKfD8182Mxm7gi6LvVtRgIxHDpS mY5Mv9TtYEAYJM5kB1PSPvSMqD66AERM/96qcH1npBKYmb7RCUQcYJp9+QlV5En0qL2m vTGoMjeCKRHYEEc0CEXHwbLYs0WJFN/NuYOtc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680252324; x=1682844324; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=9R0pmSOXEmoWLF3xHrqKFR0ZIX1xVJ9vEp3dmqdHEPA=; b=ZP3UY7wYb9C/R6to+HFJPnk6tKxOU9YFOcicSd26h6CK6f+4G+yB6SJPNcyOC/0ddk 7FV6Hq/2m8LcNRQBi1NT2EemTyvaaffKZ741Jyc191wEfsknYljLd9riwK7YrS8aQx9X CHIJjDnHuq3mADMgyExIyXRkGRz6wVOaCPE552/o5Pu5HHWRKNckdibps8VIIVYWvjD2 wv4yeCy0ZX1ZXKD2mUuvWAB+NNbW9NSsEHcTgX0isLNdQRQcgp1L+nywdAX3/q23MUdS nlyvLDNAHNveVnpiC4u6TZsTFc6HI/zOB/XO6js1Z3CYnbX9jTSJSJeXJ0ueVYZT4cMT NI/A==
X-Gm-Message-State: AAQBX9dlMVr4SL2jPTDB8ZrzSs7vq2QMB7LKDny6k9pc7HDuyJxkhdzL GTG568F1UcnvI1oilPsZsfycRJoD3aQnzeGBKLc=
X-Google-Smtp-Source: AKy350ZpDKW31m36YFyoPtx5a4tMrb2d1V/MQYd0cDgTSpLOQJo7r7JWECm1VWweY/yUblY1gcnG/g==
X-Received: by 2002:a05:6214:401a:b0:5ab:8be1:6182 with SMTP id kd26-20020a056214401a00b005ab8be16182mr7689834qvb.5.1680252323712; Fri, 31 Mar 2023 01:45:23 -0700 (PDT)
Received: from smtpclient.apple ([185.199.103.122]) by smtp.gmail.com with ESMTPSA id k18-20020ac84792000000b003e4c6b2cc35sm487623qtq.24.2023.03.31.01.45.22 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 31 Mar 2023 01:45:23 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.300.101.1.3\))
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <FR3P281MB15034E9C4A21BC7CCE1320AAF9889@FR3P281MB1503.DEUP281.PROD.OUTLOOK.COM>
Date: Fri, 31 Mar 2023 11:45:09 +0300
Cc: "A. Jean Mahoney" <mahoney@nostrum.com>, lionel.morand@orange.com, eckelcu@cisco.com, R.Jesske@telekom.de
Content-Transfer-Encoding: quoted-printable
Message-Id: <704D3725-AD5F-479B-B935-31397236E196@brianrosen.net>
References: <FR2P281MB0028D7978CDBF03D63BD8D5EF93F9@FR2P281MB0028.DEUP281.PROD.OUTLOOK.COM> <FR3P281MB15034D841CB31D80DF059070F9889@FR3P281MB1503.DEUP281.PROD.OUTLOOK.COM> <FR3P281MB15034E9C4A21BC7CCE1320AAF9889@FR3P281MB1503.DEUP281.PROD.OUTLOOK.COM>
To: SIPCORE <sipcore@ietf.org>
X-Mailer: Apple Mail (2.3731.300.101.1.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/J0mONpdrBZ2otk4xmjObuXyKVsg>
Subject: Re: [sipcore] Activity proposal on: New Version Notification for draft-jesske-update-p-visited-network-03.txt
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Mar 2023 08:45:30 -0000
Folks, this is a very short draft that seems to be a simple fix to an actual problem. Could you please review it and bring any issues you may have with it forward? Barring any such issues, chairs will start a WGLC soon. Brian > On Mar 28, 2023, at 7:43 AM, R.Jesske@telekom.de wrote: > > Sorry, > missed to point to the mail archive with the recommendation out of the former days and what to do. > > https://mailarchive.ietf.org/arch/browse/sipcore/?gbt=1&q=P-visited > > So I would be happy to finalize the work and procced with the process. > > Thank you and Best Regards > > Roland > > -----Ursprüngliche Nachricht----- > Von: sipcore <sipcore-bounces@ietf.org> Im Auftrag von Jesske, Roland > Gesendet: Dienstag, 28. März 2023 06:30 > An: sipcore@ietf.org; mahoney@nostrum.com; br@brianrosen.net > Cc: lionel.morand@orange.com; eckelcu@cisco.com > Betreff: Re: [sipcore] Activity proposal on: New Version Notification for draft-jesske-update-p-visited-network-03.txt > > Hi, > since we had today a F2F coordination meeting for 3GPP/IETF and discussed the dependencies. > There is still the dependency of an Draft meant to be informal for an description how a P-header should behave. > > Question is how we can pickup the activity again? > > https://datatracker.ietf.org/doc/draft-jesske-update-p-visited-network/ > > It is a very small draft. > > Thank you and Best Regards > > Roland > > -----Ursprüngliche Nachricht----- > Von: Jesske, Roland > Gesendet: Montag, 31. Mai 2021 14:23 > An: sipcore@ietf.org > Cc: lionel.morand@orange.com > Betreff: Activity proposal on: New Version Notification for draft-jesske-update-p-visited-network-03.txt > > > Dear all, > There is still an issue that is open with regard to dependencies we have with 3GPP. > Referring to: > > https://mailarchive.ietf.org/arch/msg/sipcore/86gDbPVcITa4HH4Mg3qLh0LbCMQ/ > > It would be nice if we can take the activity now and finalize the below mentioned draft. > > Seen from 3GPP perspective it would be important to finalize this activity that we can proceed with the final solution. > > Thank you and Best Regards > > Roland > > -----Ursprüngliche Nachricht----- > Von: internet-drafts@ietf.org <internet-drafts@ietf.org> > Gesendet: Montag, 31. Mai 2021 14:16 > An: Jesske, Roland <R.Jesske@telekom.de> > Betreff: New Version Notification for draft-jesske-update-p-visited-network-03.txt > > > A new version of I-D, draft-jesske-update-p-visited-network-03.txt > has been successfully submitted by Roland Jesske and posted to the IETF repository. > > Name: draft-jesske-update-p-visited-network > Revision: 03 > Title: Update to Private Header Field P-Visited-Network-ID in Session Initiation Protocol (SIP) Requests and Responses > Document date: 2021-05-31 > Group: Individual Submission > Pages: 4 > URL: https://www.ietf.org/archive/id/draft-jesske-update-p-visited-network-03.txt > Status: https://datatracker.ietf.org/doc/draft-jesske-update-p-visited-network/ > Htmlized: https://datatracker.ietf.org/doc/html/draft-jesske-update-p-visited-network > Diff: https://www.ietf.org/rfcdiff?url2=draft-jesske-update-p-visited-network-03 > > Abstract: > The Third Generation Partnership Project (3GPP) has identified cases > where the private header field P-Visited-Network-ID SIP private > header extensions, which is defined in RFC 7315 and updated by RFC > 7976, needs to be included in SIP requests and responses. This > document updates RFC 7976, in order to allow inclusion of the P- > Visited-Network-ID header field in responses. > > > > > The IETF Secretariat > > > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore
- [sipcore] Activity proposal on: New Version Notif… R.Jesske
- Re: [sipcore] Activity proposal on: New Version N… R.Jesske
- Re: [sipcore] Activity proposal on: New Version N… R.Jesske
- Re: [sipcore] Activity proposal on: New Version N… Brian Rosen
- Re: [sipcore] Activity proposal on: New Version N… lionel.morand
- Re: [sipcore] Activity proposal on: New Version N… worley