Richard Shockey | 3 Mar 2003 22:02
Picon

Agenda for ENUM WG IETF 56


WEDNESDAY, March 19, 2003
0800-1700 IETF Registration -
0800-0900 Continental Breakfast -
0900-1130 Morning Sessions
APP     calsch    Calendaring and Scheduling WG
OPS     v6ops     IPv6 Operations WG
TSV     dccp      Datagram Congestion Control Protocol WG
TSV     enum      Telephone Number Mapping WG

*************

IETF 56 San Francisco Telephone Number Mapping (ENUM) WG  Agenda

Chair(s):
Patrik Faltstrom <paf <at> cisco.com>
Richard Shockey <rich.shockey <at> neustar.biz>

Transport Area Advisor:
TBD

Mailing Lists:
General Discussion:enum <at> ietf.org
To Subscribe: enum-request <at> ietf.org
In Body: subscribe
Archive: ftp://ftp.ietf.org/ietf-mail-archive/enum/


AGENDA BASHING (5 min)

(Continue reading)

Michael Mealling | 4 Mar 2003 15:45

Re: I-D ACTION:draft-ietf-enum-rfc2916bis-04.txt

Just before I sent this out there were some additional comments
concerning the DNSSEC issue. I decided not to put my proposed text in
there since I think the issue probably needs some (hopefully short)
discussion in the meeting. As far as I can tell once that text is
changed the document should be done (although I would like some more
examples)...

-MM

On Tue, 2003-03-04 at 07:29, Internet-Drafts <at> ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Telephone Number Mapping Working Group of the IETF.
> 
> 	Title		: The E.164 to URI DDDS Application (ENUM)
> 	Author(s)	: P. Faltstrom, M. Mealling
> 	Filename	: draft-ietf-enum-rfc2916bis-04.txt
> 	Pages		: 21
> 	Date		: 2003-3-3
Richard Shockey | 4 Mar 2003 15:56
Picon

RE: rfc2916bis-04.txt


I want to emphasize as strongly as I can that the WG read the 04 draft very 
carefully as it is the candidate for last call.

If it is agreeable to the WG, in the absence of substantive comments over 
the next 5 working days I'll issue last call.

 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
Voice +1 571.434.5651 Cell : +1 314.503.0640,  Fax: +1 815.333.1237
<mailto:richard <at> shockey.us> or <mailto:richard.shockey <at> neustar.biz>
  <http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Richard Shockey | 4 Mar 2003 16:00
Picon

Re: I-D ACTION:draft-ietf-enum-rfc2916bis-04.txt

At 09:45 AM 3/4/2003 -0500, Michael Mealling wrote:
>Just before I sent this out there were some additional comments
>concerning the DNSSEC issue. I decided not to put my proposed text in
>there since I think the issue probably needs some (hopefully short)
>discussion in the meeting. As far as I can tell once that text is
>changed the document should be done (although I would like some more
>examples)...

OK .. thats fine with me ...we'll hold off any last call until after 
SF  I'm assuming now that we need an 05.

 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
Voice +1 571.434.5651 Cell : +1 314.503.0640,  Fax: +1 815.333.1237
<mailto:richard <at> shockey.us> or <mailto:richard.shockey <at> neustar.biz>
  <http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Michael Mealling | 4 Mar 2003 16:21

Re: RE: rfc2916bis-04.txt

On Tue, 2003-03-04 at 09:56, Richard Shockey wrote:
> I want to emphasize as strongly as I can that the WG read the 04 draft very 
> carefully as it is the candidate for last call.
> 
> If it is agreeable to the WG, in the absence of substantive comments over 
> the next 5 working days I'll issue last call.

I know of two issues that need to be discussed:

1) final agreement on DNSSEC wording
2) any additional text on the partial e.164 number issue

-MM
Jeff Williams | 4 Mar 2003 23:18
Picon

Re: RE: rfc2916bis-04.txt

Michael and all,

  I agree with Michael here...

Michael Mealling wrote:

> On Tue, 2003-03-04 at 09:56, Richard Shockey wrote:
> > I want to emphasize as strongly as I can that the WG read the 04 draft very
> > carefully as it is the candidate for last call.
> >
> > If it is agreeable to the WG, in the absence of substantive comments over
> > the next 5 working days I'll issue last call.
>
> I know of two issues that need to be discussed:
>
> 1) final agreement on DNSSEC wording
> 2) any additional text on the partial e.164 number issue
>
> -MM
>
> _______________________________________________
> enum mailing list
> enum <at> ietf.org
> https://www1.ietf.org/mailman/listinfo/enum

--
Jeffrey A. Williams
Spokesman for INEGroup LLA. - (Over 129k members/stakeholders strong!)
================================================================
CEO/DIR. Internet Network Eng. SR. Eng. Network data security
(Continue reading)

Stastny Richard | 5 Mar 2003 05:17
Picon

AW: I-D ACTION:draft-ietf-enum-rfc2916bis-04.txt

Hi Rich and MM,

was it really necessary to introduce so much new text in 04? I hoped to have
rfc2916bis from the table soon, but with all this new text in section 1.3, 2.4, 2.5, 2.6
and wherever else I have a problem. I need to discuss and understand the impact of all these issues
so IMHO it is not yet possible to have a last call now.

So I also agree to hold off last call until SFO.

best regards
Richard Stastny

	-----Ursprüngliche Nachricht----- 
	Von: Richard Shockey [mailto:richard <at> shockey.us] 
	Gesendet: Di 04.03.2003 16:00 
	An: Michael Mealling; enum <at> ietf.org 
	Cc: 
	Betreff: Re: [Enum] I-D ACTION:draft-ietf-enum-rfc2916bis-04.txt
	
	

	At 09:45 AM 3/4/2003 -0500, Michael Mealling wrote:
	>Just before I sent this out there were some additional comments
	>concerning the DNSSEC issue. I decided not to put my proposed text in
	>there since I think the issue probably needs some (hopefully short)
	>discussion in the meeting. As far as I can tell once that text is
	>changed the document should be done (although I would like some more
	>examples)...
	
	OK .. thats fine with me ...we'll hold off any last call until after
(Continue reading)

Conroy, Lawrence (SMTP | 5 Mar 2003 12:21
Picon

Re: I-D ACTION:draft-ietf-enum-rfc2916bis-04.txt

At 9:45 am -0500 4/3/03, Michael Mealling wrote:
>Just before I sent this out there were some additional comments
>concerning the DNSSEC issue. I decided not to put my proposed text in
>there since I think the issue probably needs some (hopefully short)
>discussion in the meeting. As far as I can tell once that text is
>changed the document should be done (although I would like some more
>examples)...

Hi Folks,
   in the examples of 4.1, enumservice "msg" is given (twice).
I guess that this "crossed" with the update to/replacement of the earlier
evil 'compendium' draft, and will be changed to "email". Correct?

On the topic, I also am not sure this is quite ready for WGLC, as I
need to understand the new text; I look forward to the SF meeting.

atb,
   Lawrence
--

-- 
-----------------------------------------------------------------------
Roke Manor Research    : This information is provided "as is" and is not
<mailto:lwc <at> roke.co.uk>: intended to create any contractual or legal
<tel:+441794833666>    : relationship.
Michael Mealling | 5 Mar 2003 15:50

Re: AW: I-D ACTION:draft-ietf-enum-rfc2916bis-04.txt

On Tue, 2003-03-04 at 23:17, Stastny Richard wrote:
> was it really necessary to introduce so much new text in 04? 

It was based on issues people brought up on the list so as the document
author I'm duty bound to reflect list consensus in the document.Plus
some sections (like 1.3) were simply incorrect but needed more text to
explain what the real issue was.

None of the changes are substantive. Nothing technical has changed with
how ENUM works at all. Just explanatory text.

> I hoped to have
> rfc2916bis from the table soon, but with all this new text in section 1.3, 2.4, 2.5, 2.6
> and wherever else I have a problem. I need to discuss and understand the impact of all these issues
> so IMHO it is not yet possible to have a last call now.
>  
> So I also agree to hold off last call until SFO.

Feel free to bug me directly if you have questions about the new text...

-MM
Richard Shockey | 5 Mar 2003 16:05
Picon

Re: AW: I-D ACTION:draft-ietf-enum-rfc2916bis-04.txt

At 05:17 AM 3/5/2003 +0100, Stastny Richard wrote:
>Hi Rich and MM,
>
>was it really necessary to introduce so much new text in 04? I hoped to have
>rfc2916bis from the table soon, but with all this new text in section 1.3, 
>2.4, 2.5, 2.6
>and wherever else I have a problem. I need to discuss and understand the 
>impact of all these issues
>so IMHO it is not yet possible to have a last call now.
>
>So I also agree to hold off last call until SFO.

OK I agree but get your comments to the list ASAP...

We all agree that it is essential this work move forward quickly.

>
>best regards
>Richard Stastny
>

 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
Voice +1 571.434.5651 Cell : +1 314.503.0640,  Fax: +1 815.333.1237
<mailto:richard <at> shockey.us> or <mailto:richard.shockey <at> neustar.biz>
  <http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
(Continue reading)


Gmane