Re: [sipcore] draft-jesske-update-p-visited-network-07.txt
Brian Rosen <br@brianrosen.net> Thu, 04 January 2024 01:05 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 7A562C1516EA for <sipcore@ietfa.amsl.com>; Wed, 3 Jan 2024 17:05:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 dU-uB2yfgyq4 for <sipcore@ietfa.amsl.com>; Wed, 3 Jan 2024 17:05:45 -0800 (PST)
Received: from mail-qv1-xf36.google.com (mail-qv1-xf36.google.com [IPv6:2607:f8b0:4864:20::f36]) (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 06E25C1516E9 for <sipcore@ietf.org>; Wed, 3 Jan 2024 17:05:45 -0800 (PST)
Received: by mail-qv1-xf36.google.com with SMTP id 6a1803df08f44-67f9b98e555so64146d6.0 for <sipcore@ietf.org>; Wed, 03 Jan 2024 17:05:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen.net; s=google; t=1704330344; x=1704935144; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=4umHwdYqoj2MoLaL5rrSPAwcEMRC17V1lOOGrW6sEr4=; b=fjdxb487yPWaSrDtRMs7ESTEbbIMO3yW1LMn1JaiEArUzVDqJufoE3rYwqeHv3mK/d wRKDip/1rYRqwZBQrD+zFdpvoYRMnN6lDvMfJFn03/0DLQ+nrZof2SJBXAqPV5BkkJLf uPwODVE8AfF74f/bAreFDcUvZlDTeH9/Ldbjo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704330344; x=1704935144; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=4umHwdYqoj2MoLaL5rrSPAwcEMRC17V1lOOGrW6sEr4=; b=VFMu6JeMmPyPg9k8z/tja26dhehRe4OyXKRzk1toA2y/CfmHBDtBF4y7pI+839IHza QxcPsFBtd40/SnFdZKNk8UH1Mis2pNQrGC4Cv8HIf0X2cNEpgmnp+W/nFr4I/c20UgRA ML6dIabz70TWXWc+LN5+fceWGjYtIu2IfAddB7SSGt/WDPLEqBHlbHIGUN6D2m8TDLLs mIOsnANQdHMN11KWfEBgqINi1syf2JH2GoPTlS09raghGG+UmnzIO/ad/kA+OCsog3Xw 2pV3s48BG+xb1nQG10PQuiRHVm1RhbFdLj/6GkJh33Iv73hGNiUFKy7KpHe1SSbQhhKI zHMQ==
X-Gm-Message-State: AOJu0Yw1cbCsypf1lz723EJvNIc6GapMrsPuZdsS7cvuUc+T2/pDHMO+ QdKowigxjEj52QpPY0GRBr/x7/MCZfZUYQ==
X-Google-Smtp-Source: AGHT+IGssmKrZZr3xbuGByFlxfiFTjyCPR1sL15ttYW8CC0PRztZUr2RdGZO5h8yLlWDBG3dy53rMg==
X-Received: by 2002:a05:6214:2609:b0:680:c21c:2ab5 with SMTP id gu9-20020a056214260900b00680c21c2ab5mr6569534qvb.6.1704330343919; Wed, 03 Jan 2024 17:05:43 -0800 (PST)
Received: from smtpclient.apple (dynamic-acs-24-154-121-237.zoominternet.net. [24.154.121.237]) by smtp.gmail.com with ESMTPSA id bq14-20020a05620a468e00b00781d60d3597sm1906098qkb.120.2024.01.03.17.05.43 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Jan 2024 17:05:43 -0800 (PST)
From: Brian Rosen <br@brianrosen.net>
Message-Id: <8E66F992-4F8B-4D9D-AE23-2ABA69C21684@brianrosen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_390C1BD8-5CFF-48D4-B2AC-50F2A32BC647"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.100.2.1.4\))
Date: Wed, 03 Jan 2024 20:05:38 -0500
In-Reply-To: <FR3P281MB15032435075CB01CD3D38A5EF99DA@FR3P281MB1503.DEUP281.PROD.OUTLOOK.COM>
Cc: eckelcu@cisco.com, sipcore@ietf.org
To: R.Jesske@telekom.de
References: <BF5DB869-8E78-4550-8685-F9A8D225BED3@cisco.com> <FR3P281MB1503EA4C50B90F0C91165DC9F9DFA@FR3P281MB1503.DEUP281.PROD.OUTLOOK.COM> <4569DC3E-FD38-45B4-9DA1-FF87571ECAF6@cisco.com> <FR3P281MB15032435075CB01CD3D38A5EF99DA@FR3P281MB1503.DEUP281.PROD.OUTLOOK.COM>
X-Mailer: Apple Mail (2.3774.100.2.1.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/LNKlsZ0_MYl2qigrnkMq_odQB5w>
Subject: Re: [sipcore] draft-jesske-update-p-visited-network-07.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: Thu, 04 Jan 2024 01:05:49 -0000
<As chair> This message starts a two week call for adoption of the draft, with the intention that it will be reworked as needed and re-named to rfc7976bis. Please send comments to the list. Roland, assuming the WG agrees to adopt the draft, we will ask you to submit it as draft-ietf-sipcore-rfc7976bis-00. We will also ask you to make sure that the errata identified in 7976 are addressed. The data tracker will note the prior versions correctly once we set it up. Brian > On Dec 29, 2023, at 4:17 AM, R.Jesske@telekom.de wrote: > > Dear all, > I have uploaded a new version. > > URL: https://www.ietf.org/archive/id/draft-jesske-update-p-visited-network-07.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://author-tools.ietf.org/iddiff?url2=draft-jesske-update-p-visited-network-07 > > Of course comments are welcome. > > The main change to the RFC7976 is that P-Visited-Network-ID header field can appear in all responses except for 100 (Trying). > > As commented during the WGLC it was proposed to change the behaviour from UPDATE to an BIS draft. > > Since there are no objections from people could I get some advice from the SIPCORE chair if I can now create an sipcore RFC7976bis draft, to start the official procedure to go forward to an RFC or is there another procedure seen? > > Thank you and Best Regards > > Roland > > Von: Charles Eckel (eckelcu) <eckelcu@cisco.com <mailto:eckelcu@cisco.com>> > Gesendet: Freitag, 3. November 2023 16:08 > An: Jesske, Roland <R.Jesske@telekom.de <mailto:R.Jesske@telekom.de>> > Cc: sipcore@ietf.org <mailto:sipcore@ietf.org> > Betreff: Re: [sipcore] Working Group Last Call draft-jesske-update-p-visited-network-03.txt > > Hi Roland, > > Not hearing any objections, that seems a good way to proceed. > > Cheers, > Charles > > > On Oct 24, 2023, at 9:03 AM, R.Jesske@telekom.de <mailto:R.Jesske@telekom.de> wrote: > > Hi Charles, > Thank you for binging this up. > It was the proposal to change then the naming to an rfc7976_bis and I have provided an Update https://datatracker.ietf.org/doc/draft-jesske-update-p-visited-network/ in Summer to use the RFC7976 as baseline. > > The proposal was discussed to change it to an rfc7976_bis and I saw some agreement but not a final decision. > > If people are happy with that approach then I recheck the draft and could provide this draft as an bis draft. > > Best Regards > > Roland > Von: sipcore <sipcore-bounces@ietf.org <mailto:sipcore-bounces@ietf.org>> Im Auftrag von Charles Eckel (eckelcu) > Gesendet: Montag, 23. Oktober 2023 23:41 > An: sipcore@ietf.org <mailto:sipcore@ietf.org> > Betreff: Re: [sipcore] Working Group Last Call draft-jesske-update-p-visited-network-03.txt > > Apologies for reviving an old thread, but draft-jesske-update-p-visited-network came up in our dependencies discussion during the IETF-3GPP coordination call today [1] and I wanted to check on next steps. > > We are putting together the agenda for the IETF-3GPP coordination meeting at IETF 118 and could allocate some time for a discussion on this draft in that forum if it would be helpful. > > Cheers, > Charles > > [1] https://datatracker.ietf.org/iabasg/ietf3gpp/meetings/ > > _______________________________________________ > sipcore mailing list > sipcore@ietf.org <mailto:sipcore@ietf.org> > https://www.ietf.org/mailman/listinfo/sipcore
- [sipcore] Working Group Last Call draft-jesske-up… Brian Rosen
- Re: [sipcore] Working Group Last Call draft-jessk… Paul Kyzivat
- Re: [sipcore] Working Group Last Call draft-jessk… Paul Kyzivat
- Re: [sipcore] Working Group Last Call draft-jessk… R.Jesske
- Re: [sipcore] Working Group Last Call draft-jessk… Paul Kyzivat
- Re: [sipcore] Working Group Last Call draft-jessk… R.Jesske
- Re: [sipcore] Working Group Last Call draft-jessk… Ranjit Avasarala (Nokia)
- Re: [sipcore] Working Group Last Call draft-jessk… Paul Kyzivat
- Re: [sipcore] Working Group Last Call draft-jessk… Christer Holmberg
- Re: [sipcore] Working Group Last Call draft-jessk… Paul Kyzivat
- Re: [sipcore] Working Group Last Call draft-jessk… Christer Holmberg
- Re: [sipcore] Working Group Last Call draft-jessk… Charles Eckel (eckelcu)
- Re: [sipcore] Working Group Last Call draft-jessk… R.Jesske
- Re: [sipcore] Working Group Last Call draft-jessk… Charles Eckel (eckelcu)
- [sipcore] draft-jesske-update-p-visited-network-0… R.Jesske
- Re: [sipcore] draft-jesske-update-p-visited-netwo… Brian Rosen
- Re: [sipcore] draft-jesske-update-p-visited-netwo… Paul Kyzivat
- Re: [sipcore] draft-jesske-update-p-visited-netwo… Charles Eckel (eckelcu)
- Re: [sipcore] draft-jesske-update-p-visited-netwo… R.Jesske