Paul Hoffman <paul.hoffman@xxxxxxxx> wrote:
> Sean's exactly right here. Having to add a lot of new text to the
> abstract basically makes it a mini-introduction. Instead, please
> consider:
> The specific reasons that a given RFC updates another should be
> described near the top of the Introduction section of the new RFC,
> possibly in its own sub-section. This text should contain enough detail
> to help readers who are familiar with the specification that is being
> updated to decide if they need to read the rest of this newer RFC. This
> text must contain enough detail for readers to fully understand the
> nature of the update.
well said.
--
Michael Richardson <mcr+IETF@xxxxxxxxxxxx>, Sandelman Software Works
-= IPv6 IoT consulting =-
Attachment:
signature.asc
Description: PGP signature
