TRILL: RBridge Channel Tunnel Protocol
<draft-ietf-trill-channel-tunnel-05.txt>

corrections::
page 16 4.5 RFC 5310 Based Authentication
["or" should be "on"]
(as written)
   o RESV: Six bits that MUST be sent as zero and ignored or receipt.
(should be)
   o RESV: Six bits that MUST be sent as zero and ignored on receipt
---------------------------------------------------------

page 17 4.5 RFC 5310 Based Authentication
[second "that" probably should be "the" or not there at all]
(as written)
o Key ID: specifies the same keying value and authentication
      algorithm that that Key ID specifies for TRILL IS-IS LSP [RFC5310]
      Authentication TLVs.
(probably should be)
o Key ID: specifies the same keying value and authentication
      algorithm that Key ID specifies for TRILL IS-IS LSP [RFC5310]
      Authentication TLVs.
(could be)
o Key ID: specifies the same keying value and authentication
      algorithm that the Key ID specifies for TRILL IS-IS LSP [RFC5310]
      Authentication TLVs.
----------------------------------------------------

page 22   7. Security Considerations  third paragraph first sentence
['taking" should be "taken"]
(as written)
   On the negative side, the optional ability to tunnel various payload
   types and to tunnel them between TRILL switches and to and from end
   stations can increase risk unless precautions are taking.
(should be)
   On the negative side, the optional ability to tunnel various payload
   types and to tunnel them between TRILL switches and to and from end
   stations can increase risk unless precautions are taken.
---------------------------------------------------------

page 22 Security Considerations  third paragraph second sentence
[sentence is a bit "run on". I'd at least add a comma if breaking it 
into two sentences doesn't appeal to you.
(as written)
The processing of decapsulating Tunnel Protocol payloads is not a 
good place to be liberal in what you accept as the tunneling facility 
makes it easier for unexpected messages to pop up in unexpected 
places in a TRILL campus due to accidents or the actions of an adversary.
(could be)
The processing of decapsulating Tunnel Protocol payloads is not a 
good place to be liberal in what you accept, as the tunneling 
facility makes it easier for unexpected messages to pop up in 
unexpected places in a TRILL campus due to accidents or the actions 
of an adversary.
(maybe)
The processing of decapsulating Tunnel Protocol payloads is not a 
good place to be liberal in what you accept. This is because the 
tunneling facility makes it easier for unexpected messages to pop up 
in unexpected places in a TRILL campus due to accidents or the 
actions of an adversary.

============================================

Just a Note::
Page 3
CCM is defined as Continuity Check Message in other TRILL documents. 
It is defined Counter with CBC-MAC (Cypher Block Chaining - Message 
Authentication Code) in the draft.