RE: Gen-ART LC review of draft-ietf-pcp-description-option-03

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Re-,

The description is used by the entity managing the PCP server. The document does not elaborate on such usage as this is deployment-specific: e.g.,  (1) it can be used as  helper to clean the mapping table, (2) in some deployments that make use of a portal to instruct pcp mappings, this option can be used to store a subscriber-identifier, etc. We can add some text if you think this is useful to be mentioned in the document.

For the second point, I updated Section 5 with a pointer to Section 2. Thanks.

Cheers,

Med

De : Roni Even [mailto:ron.even.tlv@xxxxxxxxx]
Envoyé : lundi 27 janvier 2014 10:31
À : BOUCADAIR Mohamed IMT/OLN; draft-ietf-pcp-description-option.all@xxxxxxxxxxxxxx
Cc : ietf@xxxxxxxx; gen-art@xxxxxxxx
Objet : RE: Gen-ART LC review of draft-ietf-pcp-description-option-03

 

Hi Med,

Inline

Roni

 

From: mohamed.boucadair@xxxxxxxxxx [mailto:mohamed.boucadair@xxxxxxxxxx]
Sent: 27 January, 2014 10:31 AM
To: Roni Even; draft-ietf-pcp-description-option.all@xxxxxxxxxxxxxx
Cc: ietf@xxxxxxxx; gen-art@xxxxxxxx
Subject: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03

 

Dear Roni,

Thank you for the review.

Please see inline.

Cheers,

Med

De : Roni Even [mailto:ron.even.tlv@xxxxxxxxx]
Envoyé : dimanche 26 janvier 2014 09:13
À : draft-ietf-pcp-description-option.all@xxxxxxxxxxxxxx
Cc : ietf@xxxxxxxx; gen-art@xxxxxxxx
Objet : Gen-ART LC review of draft-ietf-pcp-description-option-03

 

I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you may receive.

Document:  draft-ietf-pcp-description-option-03

Reviewer: Roni Even

Review Date:2014–1-26

IETF LC End Date: 2014–2-4

IESG Telechat date:

 

Summary: This draft is almost ready for publication as a standard track RFC.

 

 

Major issues:

 

Minor issues:

 

1.       I am not sure what the use of the “description” option is. I can see how to create one but as for usage the only text I can see is “Querying the PCP server to get the description text of an existing mapping is out of scope.” I think that the document should provide information about the purpose of this option.

[Med] The main usage is for a user to associate a textual description with a mapping. This is captured by this text “   This option can be used by a user (or an application) to indicate a

   description associated with a given mapping such as "FTP server", "My

   remote access to my CP router", "Camera", "Network attached storage

   serve", etc.

[Roni Even] This is motivation but it is not clear why the user does it if no one can see it or does anything with it. It is kept on the server but not used by anyone?

 

Nits/editorial comments:

  1. The IANA section should provide enough information to fill the registry http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml#options

[Med] Required information as per RFC6887 is provided in http://tools.ietf.org/html/draft-ietf-pcp-description-option-03#section-2.

[Roni Even] So section 5 should point to the definition is section 2

 

 


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]