Fernando, > From: Fernando Gont [mailto:ferna...@gont.com.ar] > > On 26/2/20 11:37, bruno.decra...@orange.com wrote: > > Hi Robin, > > > > I think that this was expected that this specific LC would last for more > > than 2 weeks. > > > > Summarizing and closing it is on my to do list. (I wish my to do list > > were smaller, or that I throw more $$ or contributors on action items. > > But wishing does not help much in my world.) > > > > That been said, this does not change much with regards to technical > > comments been raised: > > > > -They are either addressed, non-addressed or pending > > > > -they can be raised after the WG LC (e.g. during IETF LC or IESG review) > > > > -they can even be raised after RFC publication. And eventually can led > > to errata, bis document, deprecation... > > So... is the plan to ship a document that violates RFC8200?
The above statement was meant to say that if the technical comment is valid, its timing (e.g., the fact that it is raised after the original Last Call period) is not an argument to dismiss this technical argument. Then your question is orthogonal, and the answer to your question is 'No'. Note that that is also orthogonal as to whether "doing A" violates RFC X or not. > Should participants stop wasting time in constructive comments, and > rather work and prepare to submit a formal appeal, instead? What is not clear in " So technical review and comments are good, at all time. "? Thank you --Bruno > Thanks, > -- > Fernando Gont > e-mail: ferna...@gont.com.ar || fg...@si6networks.com > PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1 > > > _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
