Re: [dns-dir] FW: PRELIMINARY Agenda and Package for the August 11, 2011 IESG Teleconference

[Peter Koch <[e-mail]>]

Dan,

i've checked the drafts

>   o draft-ietf-mpls-p2mp-lsp-ping-17
>   o draft-ietf-mpls-lsp-ping-enhanced-dsmap-10
>   o draft-ietf-behave-ftp64-12
>   o draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-02
>   o draft-ietf-roll-of0-15
>   o draft-ietf-mpls-mldp-recurs-fec-04
>   o draft-ietf-softwire-dslite-radius-ext-04
>   o draft-ietf-msec-gdoi-update-09
>   o draft-gutmann-cms-hmac-enc-05
>   o draft-ietf-tsvwg-rsvp-security-groupkeying-10
>   o draft-ietf-decade-survey-05
>   o draft-ietf-opsawg-oam-overview-05
>   o draft-shiomoto-ccamp-switch-programming-05
>   o draft-burgin-ipsec-suiteb-profile-01
>   o draft-law-rfc4869bis-01
>   o draft-forte-lost-extensions-07
>   o draft-simpson-isis-ppp-unique-01

for a few keywords.  draft-ietf-decade-survey-05 mentions the DNS a few
times, noting to worry about.

draft-ietf-softwire-dslite-radius-ext-04 has some nits/minor issues:

o In the introduction, AFTR should be expanded once, before first use

o I'm not too familiar with RADIUS folklore, so this might be obvious to
  others, but section 4 does not clearly state which format is used
  for DS-Lite-Tunnel-Name.  Section 5 later states that
  "The data type of DS-Lite-Tunnel-Name is a string", but earlier it is suggested
  that DS-Lite-Tunnel-Name be fed with the data obtained through DHCP in
  OPTION_AFTR_NAME, which is clarly in DNS wire format.  If this option
  uses text (presentation) format instead, it would need to say whether it's
  all ASCII (A-Label) or not (where it is unlikely amnybody intended to
  use U-Labels).
  The picture at the top of page 9 suggests the DS-Lite-Tunnel-Name
  has a fixed length (of 6 octets, for taht matter), so a more open ended
  graph as used in the RADIUS RFCs might be advised.

-Peter