IETF DNS Extensions (DNSEXT) Working Group Meeting
Agenda
IETF 78
Maastricht, NL

Version 2010-07-21 b

SESSION I
2010-07-26 15:20-17:20

A.  Administration  (10 minutes) 15:20-15:30

    1.  Blue sheets &c.

    2.  Report from chairs (questions to follow up from mailing list)

B.  Existing WG items (30 mins)

    1.  draft-ietf-dnsext-rfc2671bis-edns0 [5 mins]
        a.  Document needs new editor; thanks to Michael Graff 
            for his work.

    2.  draft-ietf-dnsext-rfc2672bis-dname [5 mins]
        a.  CNAME issue.  Is this resolved?

    3.  draft-ietf-dnsext-dnssec-registry-fixes [10 mins]
        a.  proposal for language clean up.  ok?

    4.  draft-ietf-dnsext-dnssec-bis-updates [10 mins]
        a.  Issue about CD=1
        b.  Current text re: rollover and die ok?

C.  Proposed new major work item: "aliasing", "synonymy", &c. (30 mins)

    1.  BNAME, C+DNAME, other ideas.

    texts:
        draft-yao-dnsext-bname-03
        draft-sury-dnsext-cname-dname-00
        See also draft-vrang-idn-cname-00 (long expired)
          
    a.  Discussion.
    b.  Adoption of some/all. (hums)

    2.  Shadow.  

    text:
        draft-vixie-dnsext-dnsshadow-00

    a.  Discussion
    b.  Adopt? y/n (hum)

    3.  Rationale/applicability.  

    text: 
        draft-yao-dnsext-identical-resolution-01

    a.  Discussion
    b.  Adopt?  y/n (hum)
        * note: if this work is not adopted, it affects the charter
        discussion & also runs counter to our proposal from last time.

D.  Proposed new charter.  (25 mins)

The proposed charter was posted to the mailing list:  
http://www.psg.com/lists/namedroppers/namedroppers.2010/msg01836.html

    1.  Are the timelines realistic?

    2.  What do we plan to do if we don't meet those timelines?

    3.  Are there additional items or conflicts that we need to
    address?

    4.  WG supports this charter?  (hum)

E.  Returning work items (5 mins)
    1.  draft-crocker-dnssec-algo-signal-06
        In Stockholm last year, Patrik Faltstrom determined that this
        document would be needed if and only if something like
        draft-ietf-dnsext-dnssec-alg-allocation were published.  Since
        that is about to happen, this document appears to be up for
        adoption.  Patrik has agreed to be shepherd.  Are there objections?

F.  Additional work items (25 mins)

    1.  IXFR-only: draft-kerr-ixfr-only-01
        a.  Document adopted by conventions.
        b.  Timeline acceptable?
        c.  Who thinks the document ready to ship?  (hum)

    2.  xNAME RCODE clarification: draft-eastlake-dnsext-xnamercode-02
        a.  adopt? (hum)
        b.  work needed? (hum)

    3.  DNSCURVE draft: draft-dempsky-dnscurve-01
        a.  adopt? (hum)
        b.  timelines for document (to be merged to charter)

    4.  URI DNSRR: draft-faltstrom-uri-05
        a.  RR type code already requested: expert review process on
        b.  should this be a WG item?

SESSION II
2010-07-28 10:30-11:30

This session is intended to get as much input as possible from the
IETF community.  

Useful things to have read prior to this meeting (number is priority):

1.  draft-yao-dnsext-identical-resolution-01
2.  draft-yao-dnsext-bname-03
2.  draft-sury-dnsext-cname-dname-00
2.  draft-vixie-dnsext-dnsshadow-00
3.  draft-vrang-idn-cname-00 (long expired)

A.  Aliasing: what we have and what we are planning to do (10 mins)

B.  Aliasing: the problems we are trying to solve. (10 mins)

    1.  CNAME can't redirect below.

    2.  DNAME can't redirect name itself
        a.  effects for mail

    3.  Provisioning tools not up to the job of fixing above

C.  Aliasing: what we might not be able to address. (10 mins)

    1.  Most servers need to know their own names.  

    2.  More possible names -> more ways to fool people

    3.  DNSSEC assertions from aliasA to aliasB

    4.  "Second class citizen" problem

D.  Input time: please raise your issues.  Note: it is out of order,
in this session, for anyone to say, "That can't be done."  This
session is to try to get the Big Giant List of Everything Anyone
Wants.

    Note: the chairs will ask for a show of hands for how many people
    have something to say.  If there are a lot, we'll need to work
    hard on microphone discipline.  If you have long remarks or just
    can't be there and want to make a remark in advance, please post
    it to namedroppers@ops.ietf.org, or mail it to the chairs with a
    request to forward to the list.  Thanks!