[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Documents on Agenda for June 8, 2006 Telechat
That's absolutely correct. The note in the preliminary agenda us
outdated and I replaced it with:
'Legal Counsel review received and the current version includes the
changes following this review that should allow clearing Bert Wijnen's
DISCUSS.'
Dan
> -----Original Message-----
> From: owner-mreview@ops.ietf.org
> [mailto:owner-mreview@ops.ietf.org] On Behalf Of David B Harrington
> Sent: Sunday, June 04, 2006 7:00 PM
> To: 'David Kessens'; 'MIBs review'
> Subject: RE: Documents on Agenda for June 8, 2006 Telechat
>
> Hi,
>
> To be clear, draft-harrington-8021-mib-transition-03.txt
> includes the changes requested following legal review, and
> should resolve Bert's DISCUSS.
>
> dbh
>
> > -----Original Message-----
> > From: owner-mreview@ops.ietf.org
> > [mailto:owner-mreview@ops.ietf.org] On Behalf Of David Kessens
> > Sent: Sunday, June 04, 2006 8:59 AM
> > To: MIBs review
> > Subject: Documents on Agenda for June 8, 2006 Telechat
> >
> >
> > Please see below for the documents on the agenda for next telechat.
> >
> > Dan is away for a long weekend, but he would appreciate
> your comments
> > and reviews by wednesday June 7 close of business in a time zone of
> > your choice.
> >
> > Thanks,
> >
> > David Kessens
> >
> > ----- Forwarded message from IESG Secretary
> <iesg-secretary@ietf.org>
> > -----
> >
> > 2.1 WG Submissions
> > 2.1.1 New Item
> > o draft-ietf-pwe3-atm-encap-11.txt
> > Encapsulation Methods for Transport of ATM Over MPLS Networks
> > (Proposed
> > Standard) - 1 of 6
> > Note: PROTO Shepherd: Stewart Bryant
> > Token: Mark Townsley
> > o draft-ietf-imss-fc-vf-mib-02.txt
> > The Virtual Fabrics MIB (Proposed Standard) - 2 of 6
> > Token: Dan Romascanu
> > o draft-ietf-msec-mikey-rsa-r-05.txt
> > An additional mode of key distribution in MIKEY:
> > MIKEY-RSA-R (Proposed
> > Standard) - 3 of 6
> > Note: PROTO Shepherd: Ran Canetti <canetti@watson.ibm.com>
> > Token: Russ Housley
> > o draft-ietf-radext-vlan-05.txt
> > RADIUS Attributes for Virtual LAN and Priority Support
> (Proposed
> > Standard)
> > - 4 of 6
> > Note: PROTO Shepherd: David Nelson
> <dnelson@enterasys.com>. Last
> > Call
> > ends 6/9/2006
> > Token: David Kessens
> > o draft-ietf-avt-rtp-eac3-01.txt
> > RTP Payload Format for E-AC-3 Audio (Proposed Standard) - 5 of 6
>
> > Note: Colin Perkins is PROTO Shepherd
> > Token: Cullen Jennings
> > o draft-ietf-radext-delegated-prefix-01.txt
> > RADIUS Delegated-IPv6-Prefix Attribute (Proposed
> > Standard) - 6 of 6
> > Note: PROTO Shepherd: Bernard Aboba <aboba@internaut.com>. Last
> > Call
> > ends 6/9/2006.
> > Token: David Kessens
> >
> > 2.1.2 Returning Item
> > o draft-ietf-iptel-tel-np-10.txt
> > NP Parameters for the "tel" URI (Proposed Standard) - 1 of 1
> > Note: Proto Shepherd: Jonathan Rosenberg <jdrosen@cisco.com>
> > Token: Cullen Jennings
> >
> >
> > 2.2 Individual Submissions
> > 2.2.1 New Item
> > o draft-dusseault-caldav-12.txt
> > Calendaring Extensions to WebDAV (CalDAV) (Proposed
> > Standard) - 1 of 2
> > Token: Ted Hardie
> > o draft-housley-tls-authz-extns-06.txt
> > Transport Layer Security (TLS) Authorization Extensions
> (Proposed
> > Standard)
> > - 2 of 2
> > Token: Sam Hartman
> >
> > 2.2.2 Returning Item
> > NONE
> > 2.2.3 For Action
> > o draft-miller-media-type-cellml-03.txt
> > CellML Media Type (Proposed Standard) - 1 of 1
> > Token: Brian Carpenter
> >
> > 3. Document Actions
> >
> > 3.1 WG Submissions
> > Reviews should focus on these questions: "Is this document a
> > reasonable
> > contribution to the area of Internet engineering which
> it covers? If
> > not, what changes would make it so?"
> >
> > 3.1.1 New Item
> > o draft-ietf-pce-comm-protocol-gen-reqs-06.txt
> > PCE Communication Protocol Generic Requirements
> > (Informational) - 1 of 4
> > Token: Ross Callon
> > o draft-ietf-v6ops-security-overview-04.txt
> > IPv6 Transition/Co-existence Security Considerations
> > (Informational) - 2 of
> > 4
> > Note: PROTO-SHEPHERDING WG chairs: Kurt Erik Lindqvist,
> > kurtis@kurtis.pp.se
> > Token: David Kessens
> > o draft-ietf-v6ops-nap-02.txt
> > IPv6 Network Architecture Protection (Informational) - 3 of 4
> > Note: PROTO-SHEPHERDING WG chair: Kurt Erik Lindqvist,
> > kurtis@kurtis.pp.se
> > Token: David Kessens
> > o draft-ietf-v6ops-ent-analysis-05.txt
> > IPv6 Enterprise Network Analysis (Informational) - 4 of 4
> > Note: PROTO Shepherd: Fred Baker
> > Token: David Kessens
> >
> > 3.1.2 Returning Item
> > NONE
> >
> > 3.2 Individual Submissions Via AD
> > Reviews should focus on these questions: "Is this document a
> > reasonable
> > contribution to the area of Internet engineering which
> it covers? If
> > not, what changes would make it so?"
> >
> > 3.2.1 New Item
> > o draft-kosonen-mobile-xmf-mediatype-01.txt
> > Registration of media type audio/mobile-xmf
> > (Informational) - 2 of 3
> > Note: Note: David Kessens put this on the agenda for Ted (see
> > comment log)
> > Token: Ted Hardie
> > o draft-housley-gigabeam-radio-link-encrypt-00.txt
> > GigaBeam High-Speed Radio Link Encryption (Informational)
> > - 3 of 3
> > Token: Bill Fenner
> >
> > 3.2.2 Returning Item
> > o draft-harrington-8021-mib-transition-03.txt
> > Transferring MIB Work from IETF Bridge MIB WG to IEEE 802.1 WG
> > (Informational) - 1 of 1
> > Note: Legal Counsel review received - revision needed to allow
> > closing of
> > Bert Wijnen's DISCUSS.
> > Token: Dan Romascanu
> >
> > 3.3 Individual Submissions Via RFC Editor
> > The IESG will use RFC 3932 responses: 1) The IESG has not
> > found any conflict between this document and IETF work; 2) The
> > IESG thinks that this work is related to IETF work done in WG
> > <X>, but this does not prevent publishing; 3) The IESG thinks
> > that publication is harmful to work in WG <X> and recommends
> > not publishing at this time; 4) The IESG thinks that this
> > document violates the IETF procedures for <X> and should
> > therefore not be published without IETF review and IESG
> > approval; 5) The IESG thinks that this document extends an
> > IETF protocol in a way that requires IETF review and should
> > therefore not be published without IETF review and IESG
> approval.
> >
> >
> >
> > Other matters may be recorded in comments to be passed on
> > to the RFC Editor as community review of the document.
> >
> >
> > 3.3.1 New Item
> > o draft-bivens-sasp-03.txt
> > Server/Application State Protocol v1 (Informational) - 1 of 1
> > Token: Magnus Westerlund
> >
> > 3.3.2 Returning Item
> > NONE
> > 3.3.3 For Action
> > o draft-murphy-iser-telnet-04.txt
> > iSeries Telnet Enhancements (Informational) - 1 of 1
> > Note: Recommended for Response 1, Note 2. of RFC 3932.
> > Token: Ted Hardie
> >
> >
> > ----- End forwarded message -----
> >
> >
>
>
>