@@ -58,7 +58,7 @@ service Provisioning {
5858
5959 // P2MP SR-TE Policy provisioning.
6060 //
61- // RFC 9522 S5.1.1.3; draft-ietf-pim-sr-p2mp-policy P2MP SR Policy
61+ // RFC 9522 S5.1.1.3; RFC 9960 P2MP SR Policy
6262 //
6363 // Manage resources under `p2mpSrTePolicies/{policy_id}`.
6464 rpc GetP2mpSrTePolicy (GetP2mpSrTePolicyRequest ) returns (P2mpSrTePolicy ) {}
@@ -69,7 +69,7 @@ service Provisioning {
6969
7070 // P2MP SR TE Policy dynamic candidate path provisioning.
7171 //
72- // draft-ietf-pim-sr-p2mp-policy-22 S2.3 P2MP SR Policy candidate paths.
72+ // RFC 9960 S2.3 P2MP SR Policy candidate paths.
7373 //
7474 // Manage subresources under
7575 // `p2mpSrTePolicies/{policy_id}/candidatePaths/{path_id}`.
@@ -379,8 +379,7 @@ message DeleteP2pSrTePolicyCandidatePathRequest{
379379// Describes one SR TE policy from one root EK_ROUTE_FN entity in the
380380// data model to the set of EK_ROUTE_FN entities in the list of leaves.
381381//
382- // See also:
383- // - draft-ietf-pim-sr-p2mp-policy
382+ // See also RFC 9960.
384383message P2mpSrTePolicy {
385384 // The resource name of this policy.
386385 string name = 1 [(google.api.field_behavior ) = IDENTIFIER ];
@@ -420,8 +419,8 @@ message P2mpSrTePolicy {
420419 // NMTS Entity ID corresponding to the source EK_ROUTE_FN Entity
421420 // element already created within the network data model.
422421 //
423- // draft-ietf-pim-sr-p2mp-policy S2.1 SR P2MP Policy identifying
424- // tuple; "[a]n SR P2MP Policy is uniquely identified by the tuple
422+ // RFC 9960 S2.1 SR P2MP Policy identifying tuple;
423+ // "[a]n SR P2MP Policy is uniquely identified by the tuple
425424 // <Root, Tree-ID>".
426425 //
427426 // Note: SR P2P Policy color-like differentiation can be implemented
@@ -507,9 +506,8 @@ message P2mpSrTePolicyCandidatePath {
507506 uint32 discriminator = 2 ;
508507 // RFC 9256 S2.6 optional symbolic name.
509508 string symbolic_name = 3 ;
510- // draft-ietf-pim-sr-p2mp-policy-22 does not have a field corresponding
511- // to the RFC 9256 S2.7 Preference. This can be added later, should the
512- // specification change or the need arise.
509+ // RFC 9960 does not have a field corresponding to the RFC 9256 S2.7
510+ // Preference. This can be added later, should specifications evolve.
513511
514512 // Quantitative path metrics.
515513 Metrics metrics = 4 ;
0 commit comments