Re: [sipcore] Activity proposal on: New Version Notification for draft-jesske-update-p-visited-network-03.txt

[Brian Rosen <[e-mail]>]

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, [e-mail] 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 <[e-mail]> Im Auftrag von Jesske, Roland
> Gesendet: Dienstag, 28. März 2023 06:30
> An: [e-mail]; [e-mail]; [e-mail]
> Cc: [e-mail]; [e-mail]
> 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: [e-mail]
> Cc: [e-mail]
> 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: [e-mail] <[e-mail]> 
> Gesendet: Montag, 31. Mai 2021 14:16
> An: Jesske, Roland <[e-mail]>
> 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
> [e-mail]
> https://www.ietf.org/mailman/listinfo/sipcore