headers
Andrew Newton | 3 Jan 2007 23:22
Picon

Re: FW: Preliminary BOF proposals due soon

Alright, now that the holidays are over it is time to get moving on  
SIP peering provisioning. We have requested and received an ietf.org  
mailing list for PEPPERMINT.  The list info can be found here:
https://www1.ietf.org/mailman/listinfo/peppermint

A BoF proposal is forthcoming in a day or two.

-andy

On Dec 19, 2006, at 11:26 AM, David Schwartz wrote:

> I am 85% finished on an a draft describing requirements we have
> accumulated at XConnect. Hope to have this out by the end of the year.
>
> David
>
> -----Original Message-----
> From: Richard Shockey [mailto:richard@...]
> Sent: Tuesday, December 19, 2006 5:38 PM
> To: 'Andrew Newton'; 'Livingood, Jason'; 'David Meyer';
> speermint@...
> Cc: 'RAI ADs'
> Subject: [Speermint] FW: Preliminary BOF proposals due soon
>
>
>
> Andrew Newton and I will be proposing a BOF on SPEERMINT Provisioning
> issues
> for IETF 68 in Prague.
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Richard Shockey | 6 Jan 2007 03:32
Picon

FYI - proposed PEPPERMINT BOF in Prague.


Peppermint BOF

Provisioning Extensions in Peering Registries for Multimedia
INTerconnection.

Mailing Lists:

To post to this list, send your email to:

peppermint <at> ietf.org

General information about the mailing list including subscription
information is at:

https://www1.ietf.org/mailman/listinfo/peppermint

BOF chairs:

Andrew Newton [andy <at> hxr.us]

Richard Shockey [rich.shockey <at> neustar.biz]

Temporary Area Directorate: Real Time Applications (RAI)

Ultimate Area Directorate: TBD

BOF Purpose:

The ENUM and SPEERMINT working groups are working on various aspects of
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dan Maharry | 18 Jan 2007 13:30

RFC3732 App A missing change?

Hi,

Just a quick query. I see in RFC3732-bis04 that RFC3513 has been updated
to RFC4291 but that this update is not listed in Appendix A.

Also, Section 7 contains an unformatted <xref> tag. However, I'm not
sure if this is just on
http://www.ietf.org/internet-drafts/draft-hollenbeck-epp-rfc3732bis-04.t
xt where I'm viewing this document.

Dan

Dan Maharry
Technical Manager
Midcounties Co-operative Domains Ltd 

The Midcounties Co-operative is an innovative co-operative business, owned by its customers and staff in
the 9 counties it spans. We trade in a
number of retail sectors including food, travel, funerals, motors, childcare, pharmacy, post offices
and IT. We are proud to be a successful
co-operative, founded on co-operative values and principles that co-ops share throughout the world.

This e-mail is confidential and is for the named recipient(s) only. If you are not the named recipient(s)
please do not disseminate or copy this
e-mail, but please delete it and any copies from your computer. The Midcounties Co-operative has taken
reasonable precautions to ensure that
any attachment to this e-mail has been checked for viruses. However, we cannot accept liability for any
damage sustained as a result of
any such viruses and advise you to carry out your own virus checks before opening any attachment.
Furthermore, we do not accept responsibility for any
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dan Maharry | 18 Jan 2007 14:22

RFC3735 References to schemaLocation

Hello,

RFC3730 - 3734 have all been edited to remove the use of the
schemaLocation attribute in EPP, and yet the example extensions in
RFC3735, section 2.3 still use them. Is this deliberate?

Dan

Dan Maharry
Technical Manager
Midcounties Co-operative Domains Ltd 

The Midcounties Co-operative is an innovative co-operative business, owned by its customers and staff in
the 9 counties it spans. We trade in a
number of retail sectors including food, travel, funerals, motors, childcare, pharmacy, post offices
and IT. We are proud to be a successful
co-operative, founded on co-operative values and principles that co-ops share throughout the world.

This e-mail is confidential and is for the named recipient(s) only. If you are not the named recipient(s)
please do not disseminate or copy this
e-mail, but please delete it and any copies from your computer. The Midcounties Co-operative has taken
reasonable precautions to ensure that
any attachment to this e-mail has been checked for viruses. However, we cannot accept liability for any
damage sustained as a result of
any such viruses and advise you to carry out your own virus checks before opening any attachment.
Furthermore, we do not accept responsibility for any
change made to this message after it was sent by the sender. 

*** The Midcounties Co-operative works to protect our environment ***  
*** Please don't print this e-mail unless you really need to ***
(Continue reading)

Permalink | Reply | 0 comments |
headers
Hollenbeck, Scott | 18 Jan 2007 14:17
Picon
Favicon

RE: RFC3732 App A missing change?

> -----Original Message-----
> From: owner-ietf-provreg <at> cafax.se 
> [mailto:owner-ietf-provreg <at> cafax.se] On Behalf Of Dan Maharry
> Sent: Thursday, January 18, 2007 7:31 AM
> To: ietf-provreg <at> cafax.se
> Subject: [ietf-provreg] RFC3732 App A missing change?
> 
> Hi,
> 
> Just a quick query. I see in RFC3732-bis04 that RFC3513 has 
> been updated
> to RFC4291 but that this update is not listed in Appendix A.

Missed that.  The reference was changed because the document needs to
cite a version that's already at Draft standard status.

> Also, Section 7 contains an unformatted <xref> tag. However, I'm not
> sure if this is just on
> http://www.ietf.org/internet-drafts/draft-hollenbeck-epp-rfc37
> 32bis-04.t
> xt where I'm viewing this document.

Minor editorial problem.  At worst, it'll be fixed by the RFC Editor.

This document is in the IESG's hands now.  I've asked Ted Hardie (the
shepherding AD) if he wants me to fix them or if they can wait for an
IESG note or Auth48 fix.  Either way, thanks for catching them.

-Scott-
(Continue reading)

Permalink | Reply | 501 comments |
headers
Hollenbeck, Scott | 18 Jan 2007 14:54
Picon
Favicon

RE: RFC3735 References to schemaLocation

> -----Original Message-----
> From: owner-ietf-provreg <at> cafax.se 
> [mailto:owner-ietf-provreg <at> cafax.se] On Behalf Of Dan Maharry
> Sent: Thursday, January 18, 2007 8:22 AM
> To: ietf-provreg <at> cafax.se
> Subject: [ietf-provreg] RFC3735 References to schemaLocation
> 
> Hello,
> 
> RFC3730 - 3734 have all been edited to remove the use of the
> schemaLocation attribute in EPP, and yet the example extensions in
> RFC3735, section 2.3 still use them. Is this deliberate?

Yes, because that document hasn't been updated.  3735 is an
Informational document that I don't intend to update unless something
really substantial comes up.  schemaLocation isn't substantial.

-Scott-
Permalink | Reply | 0 comments |
headers
Ted Hardie | 18 Jan 2007 20:21

RE: RFC3732 App A missing change?

At 8:17 AM -0500 1/18/07, Hollenbeck, Scott wrote:
>At worst, it'll be fixed by the RFC Editor.
>
>This document is in the IESG's hands now.  I've asked Ted Hardie (the
>shepherding AD) if he wants me to fix them or if they can wait for an
>IESG note or Auth48 fix.  Either way, thanks for catching them.
>

I think AUTH48 is fine for these.   Thanks, Dan, for the detailed review.
			Ted Hardie
Permalink | Reply | 501 comments |
headers
Hollenbeck, Scott | 26 Jan 2007 13:16
Picon
Favicon

FW: ID Tracker State Update Notice: draft-hollenbeck-epp-rfc3730bis

It looks like the IESG approved the EPP -bis documents for Draft
Standard status at yesterday's telechat.  I expect that the formal
announcement will happen early next week.

Thanks to all of you who contributed to this effort.

Note: 3734bis (the TLS document) was a bit of a challenge within the
IESG due to the downref situation with TLS.  TLS is not a Draft Standard
itself and the TLS working group isn't currently working to advance a
version of TLS to Draft.  However, our dependency isn't on a particular
version of TLS.  Both of these factors allowed me to request application
of the "downref" procedures described in RFC 3967.

The IETF approved these procedures to deal with situations like this.
This document set was apparently the first to test these procedures, and
the IESG struggled through a discussion of how to apply them.  I expect
that the approval notice will contain some words to explain how the IESG
intends to apply them going forward.  We plowed some ground for the
benefit of the rest of the IETF community!

-Scott-

-----Original Message-----
From: The IESG [mailto:iesg-secretary <at> ietf.org] 
Sent: Thursday, January 25, 2007 6:00 PM
To: Hollenbeck, Scott
Subject: ID Tracker State Update Notice: draft-hollenbeck-epp-rfc3730bis

'State Changes to Approved-announcement to be sent from IESG
Evaluation::Revised ID Needed by Ted Hardie'
(Continue reading)

Permalink | Reply | 2 comments |
headers
Michael Young | 26 Jan 2007 23:10

RE: FW: ID Tracker State Update Notice: draft-hollenbeck-epp-rfc3730bis

Congratulations Scott, a plus five year effort that produced some great
results - that's got to feel good.

Michael Young 

-----Original Message-----
From: owner-ietf-provreg <at> cafax.se [mailto:owner-ietf-provreg <at> cafax.se] On
Behalf Of Hollenbeck, Scott
Sent: Friday, January 26, 2007 7:17 AM
To: ietf-provreg <at> cafax.se
Subject: [ietf-provreg] FW: ID Tracker State Update Notice:
draft-hollenbeck-epp-rfc3730bis

It looks like the IESG approved the EPP -bis documents for Draft Standard
status at yesterday's telechat.  I expect that the formal announcement will
happen early next week.

Thanks to all of you who contributed to this effort.

Note: 3734bis (the TLS document) was a bit of a challenge within the IESG
due to the downref situation with TLS.  TLS is not a Draft Standard itself
and the TLS working group isn't currently working to advance a version of
TLS to Draft.  However, our dependency isn't on a particular version of TLS.
Both of these factors allowed me to request application of the "downref"
procedures described in RFC 3967.

The IETF approved these procedures to deal with situations like this.
This document set was apparently the first to test these procedures, and the
IESG struggled through a discussion of how to apply them.  I expect that the
approval notice will contain some words to explain how the IESG intends to
(Continue reading)

Permalink | Reply | 1 comment |
headers
Hollenbeck, Scott | 29 Jan 2007 15:08
Picon
Favicon

RE: FW: ID Tracker State Update Notice: draft-hollenbeck-epp-rfc3730bis

> -----Original Message-----
> From: Michael Young [mailto:myoung <at> ca.afilias.info] 
> Sent: Friday, January 26, 2007 5:11 PM
> To: Hollenbeck, Scott; ietf-provreg <at> cafax.se
> Subject: RE: [ietf-provreg] FW: ID Tracker State Update 
> Notice: draft-hollenbeck-epp-rfc3730bis
> 
> Congratulations Scott, a plus five year effort that produced 
> some great
> results - that's got to feel good.

My "behind the scenes" EPP work started in 1999.  Eight years sure goes
by quickly.

-Scott-
Permalink | Reply | 0 comments |

Gmane