gen-art-41

- As suggested, but with a MUST instead of MAY for the max-node-multiple
  element, as the algorithm doe snot work without it.
gen-art-47

- Fixes as suggested, ajusted for the slightly different text.
gen-art-53

- Replaced all the reserved* by invalid*, even when not referenced in a
  IANA registry.
comment-21a

s/Real Internet/Internet Model/
comment-80

- Moved reference forward from 13.4.
comment-69b

- s/Relax/RELAX/
comment-84

- Fix as suggested.
comment-85

- Added the reference to RFC 2782. The forward refenece to 11.2 is
  already present at the end of the paragraph.
Update draft-ietf-p2psip-base-24.xml

Changed "if responsible for" to "is responsible for. Minor typo.
gen-art-82a

- Fix as suggested, excepted for "For example," ->I.e.," that no longer
  applies, "For Chord-RELOAD" replaced by "CHORD-RELOAD", and the
  sorting.
gen-art-63

- The original sentence did not make much sense, so I rewrote it and
  added a reference to section 7.1.
comment-116

- s/In general,/In normal operation/
- Attached was already replaced.
comment-119

- Add text for subjectAltName but no reference.
comment-123

- Fix as suggested.
comment-124

- s/chord/Chord/
- s/Chord-reload/CHORD-RELOAD/
comment-125

- Change text to say to compare IP address to bootstrap node address in
  config file.
comment-130+131+132

- Change "Registers" to "Register" in bullet 1, same for "Defines" to
  "Define" in remainder
- Add references.
- There is no ambiguity at the level the signature is calculated, but
  some text is added to remind the designer of Usages that they need to
  say how charcaters are converted to binary storage.
- s/hashed/used/
- s/after a network partition./when a network partition is being healed/
- Moved the healing paragraph to
  section 7.4.1.1.
Added experimental error messages to discussion of error messages.
comment-138

- In fact I think that the SHOULD is wrong. Let's say that a client
  connect to this peer, but using the second bullet rule of 3.2.1, which
  means that a message is always routed with a source route. The peer
  receives the message and applies the rules of 6.1.1, removing the top
  Node-ID. Next 6.1.2 applies, as the peer is not responsible for this
  client. If the peer decide that it does not have to use the connection
  in the connection table, then the message will be routed outside and
  will never reach its destination. Hence it need to be a MUST!
clarified that intermediate nodes do not verify signatures.