[sipcore] Re: draft-jesske-update-p-visited-network-07.txt

[[e-mail]]

Hi Christer,
Thank you for the review, I will incorporated this and provide a new draft.
 
Please indicate if somebody has further comments. 
I would see the draft as ready to proceed with the next steps.
 
Thank you and Best Regards
 
Roland

-----Ursprüngliche Nachricht-----
Von: Christer Holmberg <[e-mail]> 
Gesendet: Montag, 5. August 2024 12:23
An: Charles Eckel (eckelcu) <eckelcu=[e-mail]>; Paul Kyzivat <[e-mail]>
Cc: Jesske, Roland <[e-mail]>; [e-mail]; Kreipl, Michael <[e-mail]>
Betreff: RE: [sipcore] Re: draft-jesske-update-p-visited-network-07.txt

Hi,

In general everything looks good, but a couple of comments from me:

1)	I think the title of the draft should be changed, as it does not only cover P-Visited-Network-ID. Can't we use the same title as in RFC 7976?

2)	In Section 2.2, please replace " RFCs 7315 and 3455" with "[RFC7315] and [RFC3455]".

Regards,

Christer

> -----Original Message-----
> From: Charles Eckel (eckelcu) <eckelcu=[e-mail]>
> Sent: Wednesday, 24 July 2024 18.20
> To: Paul Kyzivat <[e-mail]>
> Cc: [e-mail]; [e-mail]; [e-mail]
> Subject: [sipcore] Re: draft-jesske-update-p-visited-network-07.txt
> 
> The changes look good to me as well.
> 
> Cheers,
> Charles
> 
> > On Jul 24, 2024, at 8:01 AM, Paul Kyzivat <[e-mail]> wrote:
> >
> > Hi Roland,
> >
> > It looks good!
> >
> > 	Thanks,
> > 	Paul
> >
> > On 7/24/24 3:23 AM, [e-mail] wrote:
> >> Hi Paul,
> >> new version is uploaded.
> >> Thank you for your proposal.
> >> Name:     draft-sipcore-rfc7976bis
> >> Revision: 03
> >> Title:    Update to Private Header Field P-Visited-Network-ID in Session
> Initiation Protocol (SIP) Requests and Responses
> >> Date:     2024-07-23
> >> Group:    Individual Submission
> >> Pages:    8
> >> URL:
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.i
> etf.org%2Farchive%2Fid%2Fdraft-sipcore-rfc7976bis-
> 03.txt&data=05%7C02%7Cchrister.holmberg%40ericsson.com%7C661848eb3
> e654c6b1e2c08dcabf47673%7C92e84cebfbfd47abbe52080c6b87953f%7C0%
> 7C0%7C638574313654711617%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC
> 4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C
> %7C%7C&sdata=kmj3dzE%2Ff9scHtaNZNVFQZotgFqU1VySf2HLJIWzEFw%3D
> &reserved=0
> >> Best Regards
> >> Roland
> >> -----Ursprüngliche Nachricht-----
> >> Von: Jesske, Roland
> >> Gesendet: Montag, 15. Juli 2024 07:59
> >> An: Paul Kyzivat <[e-mail]>; [e-mail]
> >> Cc: [e-mail]; Kreipl, Michael <[e-mail]>
> >> Betreff: AW: AW: [sipcore]
> >> draft-jesske-update-p-visited-network-07.txt
> >> Hi Paul,
> >> yes indeed that is that what it is to be meant.
> >> So in the next version I will update this.
> >> Thank you and Best Regards
> >> Roland
> >> -----Ursprüngliche Nachricht-----
> >> Von: Paul Kyzivat <[e-mail]>
> >> Gesendet: Freitag, 5. Juli 2024 17:37
> >> An: Jesske, Roland <[e-mail]>; [e-mail]
> >> Cc: [e-mail]; Kreipl, Michael <[e-mail]>
> >> Betreff: Re: AW: [sipcore]
> >> draft-jesske-update-p-visited-network-07.txt
> >> On 7/5/24 3:32 AM, [e-mail] wrote:
> >>> Hi Charles,
> >>> Thank you for your review and the related comments.
> >>> I have taken them on board and uploaded a new version of the draft.
> >>>
> >>> https://data/
> >>> tracker.ietf.org%2Fdoc%2Fdraft-sipcore-
> rfc7976bis%2F02%2F&data=05%7C
> >>> 02
> >>>
> %7CR.Jesske%40telekom.de%7Ca38f9ee8715e446b2d7f08dc9d086364%7Cb
> de4df
> >>> fc
> >>>
> 4b604cf68b04a5eeb25f5c4f%7C0%7C0%7C638557906611293543%7CUnkno
> wn%7CTW
> >>> Fp
> >>>
> bGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXV
> CI6
> >>> Mn
> >>>
> 0%3D%7C0%7C%7C%7C&sdata=hYmCihF%2BMJz%2Bv3h0u1YEs3PmYgLFoD
> Ut2RUNMPVq
> >>> QD
> >>> s%3D&reserved=0
> >> This is better.
> >> While looking at this I noticed something else:
> >> You use "... header field can appear in all SIP methods and non-100
> response message except ..." multiple times. I presume you meas:
> >> "... header field can appear in all SIP methods and *the associated*
> >> non-100 response messages except ...".
> >> Perhaps this is obvious, but it wouldn't hurt to say it.
> >>         Thanks,
> >>         Paul
> >>> Thank you and Best Regards
> >>>
> >>> Roland
> >>>
> >>> -----Ursprüngliche Nachricht-----
> >>> Von: Charles Eckel (eckelcu) <[e-mail]>
> >>> Gesendet: Mittwoch, 12. Juni 2024 01:33
> >>> An: Jesske, Roland <[e-mail]>
> >>> Cc: Paul Kyzivat <[e-mail]>; [e-mail]
> >>> Betreff: Re: [sipcore] draft-jesske-update-p-visited-network-07.txt
> >>>
> >>> Hi Roland,
> >>>
> >>> Thanks for submitted and sharing both the baseline and the version with
> the intended changes.
> >>> I do not have any technical concerns with the changes, but I do have a
> couple editorial suggestions.
> >>>
> >>> Section 2.2
> >>> ---
> >>> OLD
> >>> Modify statement that P-Visited-Network-ID header field can appear in
> all non 100 (Trying) responses.
> >>>
> >>> NEW
> >>> Add statement that P-Visited-Network-ID header field can appear in all
> non 100 (Trying) responses.
> >>> —
> >>>
> >>> I suggest this because no statement about responses existing previously,
> so a statement is added rather than modified.
> >>>
> >>>
> >>> Section 3
> >>> ---
> >>> OLD
> >>> The P-Visited-Network-ID header field can appear in all SIP methods
> except ACK, BYE, CANCEL, NOTIFY, PRACK, INFO, UPDATE and in any SIP non-
> 100 response message .  The P-Visited-Network-ID header field is not needed
> in the 100 (Trying) responses, since they are transmitted hop by hop, not end
> to end.
> >>>
> >>> NEW
> >>> The P-Visited-Network-ID header field can appear in all SIP methods and
> non-100 responses, except ACK, BYE, CANCEL, NOTIFY, PRACK, INFO, and
> UPDATE.
> >>> —
> >>>
> >>> I suggest this wording because it aligns with that in RFC 7976 for P-
> Access-Network-Info, P-Charging-Vector, and P-Charging-Function-Addresses.
> Justification for not including in 100 responses seems unnecessary and is not
> provided for the other P-headers in RFC 7976, so for consistency here as well
> I think it is best to leave it out for P-Visited-Network-ID.
> >>>
> >>> Cheers,
> >>> Charles
> >>>
> >>>> On Apr 9, 2024, at 5:14 AM, [e-mail] wrote:
> >>>>
> >>>> Dear all,
> >>>> now it is done I have created two versions and calld it draft-ietf-sipcore-
> rfc7976bis-00 as basline Version and draft-ietf-sipcore-rfc7976bis-01 with the
> intended changes.
> >>>>
> >>>> Link to 00 Version:
> >>>> :
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.i
> etf.org%2Farchive%2Fid%2Fdraft-sipcore-rfc7976bis-
> 00.txt&data=05%7C02%7Cchrister.holmberg%40ericsson.com%7C661848eb3
> e654c6b1e2c08dcabf47673%7C92e84cebfbfd47abbe52080c6b87953f%7C0%
> 7C0%7C638574313654724126%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC
> 4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C
> %7C%7C&sdata=IA1UQEUb69J10HfFS8yl7uqzKvz8hgRKftkCgtS3Q8o%3D&res
> erved=0
> >>>>
> >>>> Link to 01 Version
> >>>> :
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.i
> etf.org%2Farchive%2Fid%2Fdraft-sipcore-rfc7976bis-
> 01.txt&data=05%7C02%7Cchrister.holmberg%40ericsson.com%7C661848eb3
> e654c6b1e2c08dcabf47673%7C92e84cebfbfd47abbe52080c6b87953f%7C0%
> 7C0%7C638574313654733931%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC
> 4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C
> %7C%7C&sdata=T8%2FlD5E%2B2hdDGInaJCKqKZBbGKDYYVJsUTNiqQ5OSW
> M%3D&reserved=0
> >>>>
> >>>>
> >>>> For any comment I would be happy that we can proceed this work to be
> done.
> >>>> As discussed it concerns one change which is a dependency in 3GPP.
> >>>>
> >>>> Thank you and Best Regards
> >>>>
> >>>> Roland
> >>>>
> >>>> -----Ursprüngliche Nachricht-----
> >>>> Von: sipcore <[e-mail]> Im Auftrag von Paul Kyzivat
> >>>> Gesendet: Donnerstag, 4. Januar 2024 17:43
> >>>> An: [e-mail]
> >>>> Betreff: Re: [sipcore] draft-jesske-update-p-visited-network-07.txt
> >>>>
> >>>> I support this.
> >>>>
> >>>> Thanks for calling for it to be done as a bis. I would further suggest that
> the bis be done in two distinct versions. The initial version should be
> functionally identical to rfc7976. Then the next version should include all the
> desired changes. Doing it this way will help reviewers (and implementers) to
> easily see what is really new without being distracted by all the boilerplate
> and formatting changes needed just bring the old rfc up to current
> conventions.
> >>>>
> >>>>         Thanks,
> >>>>         Paul
> >>>>
> >>>> On 1/3/24 8:05 PM, Brian Rosen wrote:
> >>>>> <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, [e-mail] wrote:
> >>>>>>
> >>>>>> Dear all,
> >>>>>> I have uploaded a new version.
> >>>>>> URL:
> >>>>>> https://ww/
> >>>>>> w.ietf.org%2Farchive%2Fid%2Fdraft-jesske-update-p-visited-network
> >>>>>> &d
> >>>>>> a
> >>>>>>
> ta=05%7C02%7CR.Jesske%40telekom.de%7Cda5026efdffd45a2a03e08dc8a6e
> >>>>>> cc
> >>>>>> 8
> >>>>>>
> 0%7Cbde4dffc4b604cf68b04a5eeb25f5c4f%7C0%7C0%7C6385374556869093
> 32
> >>>>>> %7
> >>>>>> C
> >>>>>>
> Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB
> TiI
> >>>>>> 6I
> >>>>>> k
> >>>>>>
> 1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=rPiZ6xKgc3HjlTlfHGWeZ
> 6Vct
> >>>>>> bU
> >>>>>> C
> >>>>>> 15P%2BfA1LtZ1e1kY%3D&reserved=0
> >>>>>> -07.txt
> >>>>>> <https://w/
> >>>>>> ww.ietf.org%2Farchive%2Fid%2Fdraft-jesske-update-p-visited-networ
> >>>>>> &d
> >>>>>> a
> >>>>>>
> ta=05%7C02%7CR.Jesske%40telekom.de%7Cda5026efdffd45a2a03e08dc8a6e
> >>>>>> cc
> >>>>>> 8
> >>>>>>
> 0%7Cbde4dffc4b604cf68b04a5eeb25f5c4f%7C0%7C0%7C6385374556869133
> 29
> >>>>>> %7
> >>>>>> C
> >>>>>>
> Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB
> TiI
> >>>>>> 6I
> >>>>>> k
> >>>>>>
> 1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=fIev4EQ00lKePyKo8AKf
> %2BwQ
> >>>>>> g3
> >>>>>> g
> >>>>>> PxNNBOX1iwCFg3ZY8%3D&reserved=0
> >>>>>> k-07.txt>
> >>>>>> Status:
> >>>>>> https://da/
> >>>>>> tatracker.ietf.org%2Fdoc%2Fdraft-jesske-update-p-visited-networ&d
> >>>>>> at
> >>>>>> a
> >>>>>>
> =05%7C02%7CR.Jesske%40telekom.de%7Cda5026efdffd45a2a03e08dc8a6ec
> c
> >>>>>> 80
> >>>>>> %
> >>>>>>
> 7Cbde4dffc4b604cf68b04a5eeb25f5c4f%7C0%7C0%7C638537455686917064
> %7
> >>>>>> CU
> >>>>>> n
> >>>>>>
> known%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI
> 6I
> >>>>>> k1
> >>>>>> h
> >>>>>>
> aWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=PxNZ69EhUxxrq8eNYhdw0
> okIpuX
> >>>>>> qE
> >>>>>> b
> >>>>>> se%2FgzB2uMj93c%3D&reserved=0
> >>>>>> k/
> >>>>>> <https://d/
> >>>>>> atatracker.ietf.org%2Fdoc%2Fdraft-jesske-update-p-visited-netwo&d
> >>>>>> at
> >>>>>> a
> >>>>>>
> =05%7C02%7CR.Jesske%40telekom.de%7Cda5026efdffd45a2a03e08dc8a6ec
> c
> >>>>>> 80
> >>>>>> %
> >>>>>>
> 7Cbde4dffc4b604cf68b04a5eeb25f5c4f%7C0%7C0%7C638537455686920967
> %7
> >>>>>> CU
> >>>>>> n
> >>>>>>
> known%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI
> 6I
> >>>>>> k1
> >>>>>> h
> >>>>>>
> aWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=64Z7jTy7AP5tdXlHOVltN7
> Wq6Hm
> >>>>>> Ow
> >>>>>> h
> >>>>>> y1vkzQ6%2Fo%2Br3s%3D&reserved=0
> >>>>>> rk/>
> >>>>>> HTMLized:https://eur02.safelinks.protection.outlook.com/?url=http
> >>>>>>
> s%3A%2F%2Fdeu01.safelinks.protection.outlook.com%2F%3Furl%3Dhttps
> >>>>>>
> %2525&data=05%7C02%7Cchrister.holmberg%40ericsson.com%7C661848eb
> 3
> >>>>>>
> e654c6b1e2c08dcabf47673%7C92e84cebfbfd47abbe52080c6b87953f%7C0%
> 7C
> >>>>>>
> 0%7C638574313654741070%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4w
> LjAwMD
> >>>>>>
> AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&s
> da
> >>>>>>
> ta=19MvvzT4gtN%2F5XequHk%2BEBg4uFu4Ru%2Bku%2FK8bMNkhBY%3D&r
> eserve
> >>>>>> d=0
> >>>>>> 253
> >>>>>> A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-jesske-update-
> p-
> >>>>>> &d
> >>>>>> a
> >>>>>>
> ta=05%7C02%7CR.Jesske%40telekom.de%7Cda5026efdffd45a2a03e08dc8a6e
> >>>>>> cc
> >>>>>> 8
> >>>>>>
> 0%7Cbde4dffc4b604cf68b04a5eeb25f5c4f%7C0%7C0%7C6385374556869247
> 33
> >>>>>> %7
> >>>>>> C
> >>>>>>
> Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB
> TiI
> >>>>>> 6I
> >>>>>> k
> >>>>>>
> 1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=zqOmCTZSO91zOq5lBtq
> 29JPBS
> >>>>>> CW
> >>>>>> A
> >>>>>> l8FpZAB76XILzeE%3D&reserved=0
> >>>>>> visited-network
> >>>>>> <https://d/
> >>>>>> atatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-jesske-update-p-visited-
> >>>>>> &d
> >>>>>> a
> >>>>>>
> ta=05%7C02%7CR.Jesske%40telekom.de%7Cda5026efdffd45a2a03e08dc8a6e
> >>>>>> cc
> >>>>>> 8
> >>>>>>
> 0%7Cbde4dffc4b604cf68b04a5eeb25f5c4f%7C0%7C0%7C6385374556869282
> 79
> >>>>>> %7
> >>>>>> C
> >>>>>>
> Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB
> TiI
> >>>>>> 6I
> >>>>>> k
> >>>>>>
> 1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=KghsFV%2FVjg7fV%2Fd
> C6IP%2
> >>>>>> BG
> >>>>>> w
> >>>>>> adO%2BS4ebGE8yW01N0g4Hc%3D&reserved=0
> >>>>>> network>
> >>>>>> Diff:
> >>>>>> https://au/
> >>>>>> thor-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-jesske-update-p-visit
> >>>>>> &d
> >>>>>> a
> >>>>>>
> ta=05%7C02%7CR.Jesske%40telekom.de%7Cda5026efdffd45a2a03e08dc8a6e
> >>>>>> cc
> >>>>>> 8
> >>>>>>
> 0%7Cbde4dffc4b604cf68b04a5eeb25f5c4f%7C0%7C0%7C6385374556869318
> 00
> >>>>>> %7
> >>>>>> C
> >>>>>>
> Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB
> TiI
> >>>>>> 6I
> >>>>>> k
> >>>>>>
> 1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=NR5wugPLVbemPauAbN
> gc3oQbU
> >>>>>> z4
> >>>>>> J
> >>>>>> t2%2BlDgFQPcUlMOA%3D&reserved=0
> >>>>>> ed-network-07
> >>>>>> <https://a/
> >>>>>> uthor-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-jesske-update-p-visi
> >>>>>> &d
> >>>>>> a
> >>>>>>
> ta=05%7C02%7CR.Jesske%40telekom.de%7Cda5026efdffd45a2a03e08dc8a6e
> >>>>>> cc
> >>>>>> 8
> >>>>>>
> 0%7Cbde4dffc4b604cf68b04a5eeb25f5c4f%7C0%7C0%7C6385374556869352
> 34
> >>>>>> %7
> >>>>>> C
> >>>>>>
> Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB
> TiI
> >>>>>> 6I
> >>>>>> k
> >>>>>>
> 1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=hM4RZYQoNBPWbQ2k2
> 9QjpA1TY
> >>>>>> JE
> >>>>>> c
> >>>>>> qsnqg6qGqlDxUEc%3D&reserved=0
> >>>>>> ted-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) <[e-mail]
> >>>>>> <mailto:[e-mail]>> *Gesendet:*Freitag, 3.November 2023
> >>>>>> 16:08 *An:*Jesske, Roland <[e-mail]
> >>>>>> <mailto:[e-mail]>> *Cc:*[e-mail]
> >>>>>> <mailto:[e-mail]>
> >>>>>> *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,[e-mail]
> >>>>>>     <mailto:[e-mail]>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
> >>>>>>
> Updatehttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2
> Fdatatracker.ietf.org%2Fdoc%2Fdraft-jesske-update-p-visited-
> network%2F&data=05%7C02%7Cchrister.holmberg%40ericsson.com%7C661
> 848eb3e654c6b1e2c08dcabf47673%7C92e84cebfbfd47abbe52080c6b87953f
> %7C0%7C0%7C638574313654747019%7CUnknown%7CTWFpbGZsb3d8eyJW
> IjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7
> C0%7C%7C%7C&sdata=cah83Lox5KS4W9RX8W8TIjSSNHsKfNjXuTUoN%2BB5
> PsY%3D&reserved=0
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatat
> racker.ietf.org%2Fdoc%2Fdraft-jesske-update-p-visited-
> network%2F&data=05%7C02%7Cchrister.holmberg%40ericsson.com%7C661
> 848eb3e654c6b1e2c08dcabf47673%7C92e84cebfbfd47abbe52080c6b87953f
> %7C0%7C0%7C638574313654752181%7CUnknown%7CTWFpbGZsb3d8eyJW
> IjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7
> C0%7C%7C%7C&sdata=33wYODlW7bEllcm46N3Robg%2FHbT0jqK2ax6UhOFg
> 0P8%3D&reserved=0>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 <[e-mail]
> >>>>>>     <mailto:[e-mail]>>*Im Auftrag von*Charles Eckel
> >>>>>>     (eckelcu)
> >>>>>>     *Gesendet:*Montag, 23.Oktober 2023 23:41
> >>>>>>     *An:*[e-mail] <mailto:[e-mail]>
> >>>>>>     *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://d/
> >>>>>>
> atatracker.ietf.org%2Fiabasg%2Fietf3gpp%2Fmeetings%2F&data=05%7C0
> >>>>>> 2%
> >>>>>>
> 7CR.Jesske%40telekom.de%7Ca38f9ee8715e446b2d7f08dc9d086364%7Cbde
> 4
> >>>>>> df
> >>>>>>
> fc4b604cf68b04a5eeb25f5c4f%7C0%7C0%7C638557906611326481%7CUnkn
> own
> >>>>>> %7
> >>>>>>
> CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWw
> i
> >>>>>> LC
> >>>>>>
> JXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=omfDnG7MPm7YMvuYvSiTRts7Flj
> NIfUz3
> >>>>>> e5
> >>>>>> %2BQvAmbkg%3D&reserved=0
> >>>>>>
> >>>>>> <https://d/
> >>>>>>
> atatracker.ietf.org%2Fiabasg%2Fietf3gpp%2Fmeetings%2F&data=05%7C0
> >>>>>> 2%
> >>>>>> 7
> >>>>>>
> CR.Jesske%40telekom.de%7Cda5026efdffd45a2a03e08dc8a6ecc80%7Cbde4d
> >>>>>> ff
> >>>>>> c
> >>>>>>
> 4b604cf68b04a5eeb25f5c4f%7C0%7C0%7C638537455686948965%7CUnkno
> wn%7
> >>>>>> CT
> >>>>>> W
> >>>>>>
> FpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJ
> >>>>>> XV
> >>>>>> C
> >>>>>>
> I6Mn0%3D%7C0%7C%7C%7C&sdata=%2BKAMgEj9YmIJ9uEivth887RtzadEsRP
> 49YK
> >>>>>> 2W
> >>>>>> Q
> >>>>>> Lpwj0%3D&reserved=0>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> sipcore mailing list
> >>>>>> [e-mail] <mailto:[e-mail]> https://ww/
> >>>>>>
> w.ietf.org%2Fmailman%2Flistinfo%2Fsipcore&data=05%7C02%7CR.Jesske
> >>>>>> %4
> >>>>>> 0
> >>>>>>
> telekom.de%7Cda5026efdffd45a2a03e08dc8a6ecc80%7Cbde4dffc4b604cf68
> >>>>>> b0
> >>>>>> 4
> >>>>>>
> a5eeb25f5c4f%7C0%7C0%7C638537455686952357%7CUnknown%7CTWFpb
> GZsb3d
> >>>>>> 8e
> >>>>>> y
> >>>>>>
> JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
> %
> >>>>>> 7C
> >>>>>> 0
> >>>>>>
> %7C%7C%7C&sdata=0TPclGU67tigKFwrOos4V2vQsncrgSioYDGktkS52nY%3D
> &re
> >>>>>> se
> >>>>>> r
> >>>>>> ved=0
> >>>>>> <https://w/
> >>>>>>
> ww.ietf.org%2Fmailman%2Flistinfo%2Fsipcore&data=05%7C02%7CR.Jessk
> >>>>>> e%
> >>>>>> 4
> >>>>>>
> 0telekom.de%7Cda5026efdffd45a2a03e08dc8a6ecc80%7Cbde4dffc4b604cf6
> >>>>>> 8b
> >>>>>> 0
> >>>>>>
> 4a5eeb25f5c4f%7C0%7C0%7C638537455686955767%7CUnknown%7CTWFp
> bGZsb3
> >>>>>> d8
> >>>>>> e
> >>>>>>
> yJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
> >>>>>> %7
> >>>>>> C
> >>>>>>
> 0%7C%7C%7C&sdata=TXiB3%2BgCzDCfkw6eJXGIrdRqiqxmcci3v%2FZJXPNXAS
> g%
> >>>>>> 3D
> >>>>>> &
> >>>>>> reserved=0>
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> sipcore mailing list
> >>>>> [e-mail]
> >>>>> https://www/
> >>>>>
> .ietf.org%2Fmailman%2Flistinfo%2Fsipcore&data=05%7C02%7CR.Jesske%4
> >>>>> 0t
> >>>>> e
> >>>>>
> lekom.de%7Cda5026efdffd45a2a03e08dc8a6ecc80%7Cbde4dffc4b604cf68b0
> 4
> >>>>> a5
> >>>>> e
> >>>>>
> eb25f5c4f%7C0%7C0%7C638537455686959082%7CUnknown%7CTWFpbGZs
> b3d8eyJ
> >>>>> WI
> >>>>> j
> >>>>>
> oiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C
> 0%7
> >>>>> C%
> >>>>> 7
> >>>>>
> C%7C&sdata=dUz8uKGhW3NCx8BYKwv8aPRQgiJB0A%2B8N5JEdBCtn5U%3D
> &reserv
> >>>>> ed
> >>>>> =
> >>>>> 0
> >>>>
> >>>> _______________________________________________
> >>>> sipcore mailing list
> >>>> [e-mail]
> >>>> https://www/.
> >>>>
> ietf.org%2Fmailman%2Flistinfo%2Fsipcore&data=05%7C02%7CR.Jesske%40t
> >>>> el
> >>>> e
> >>>>
> kom.de%7Cda5026efdffd45a2a03e08dc8a6ecc80%7Cbde4dffc4b604cf68b04
> a5e
> >>>> eb
> >>>> 2
> >>>>
> 5f5c4f%7C0%7C0%7C638537455686962415%7CUnknown%7CTWFpbGZsb3d
> 8eyJWIjo
> >>>> iM
> >>>> C
> >>>>
> 4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C
> %7C%
> >>>> 7C
> >>>> &
> >>>>
> sdata=PMrFanykhcwljHzUwygaRVPdfJGdbd%2BSiKkka8cQ8xE%3D&reserved
> =0
> >>>
> >
> 
> _______________________________________________
> sipcore mailing list -- [e-mail] To unsubscribe send an email to
> [e-mail]