Re: Some words on the federation concept

Going back through older email, I saw this note from Otmar and (at  
least in my mail program) zero replies.  Did everyone agree with Otmar  
or did everyone miss his message in the chaos of being at IETF 71?

For what it's worth, Otmar's definition seems fine by me.

Dan

On Mar 13, 2008, at 12:45 PM, Otmar Lendl wrote:

>
> At yesterday's session, someone (I forgot, who) voiced his suspicion
> that everybody has his own view of what a federation is and what not.
>
> We need to clear that up to make progress.
>
> Here is my PoV:
>
> The definition (from terminology-16) is:
>
>  A federation is a group of SSPs which agree to receive calls from
>  each other via SIP, and who agree on a set of administrative rules  
> for
>  such calls (settlement, abuse-handling, ...) and the specific rules
>  for the technical details of the peering.
>
> (this is basically unchanged from
> http://www.enum.at/ietf/draft-lendl-sip-peering-policy-00.txt
> of december '05)
>

New version of architecture draft

Hello,

I just submitted a new version (06) of the architecture draft that should
appear shortly. It hopefully addresses all comments made to the list and at
the IETF. It also incorporate feedback from other authors.

Email headers below for reference to the comments made to the list:

------ Forwarded Message
From: "Elwell, John" <john.elwell@...>
Date: Mon, 03 Mar 2008 08:03:39 +0000
To: <speermint@...>
Subject: [Speermint] Comments on draft-ietf-speermint-architecture-05

------ Forwarded Message
From: Hadriel Kaplan <HKaplan@...>
Date: Tue, 4 Mar 2008 15:07:44 -0500
To: "speermint@..." <speermint@...>
Subject: [Speermint] Comments on draft-ietf-speermint-architecture-05

------ Forwarded Message
From: Hadriel Kaplan <HKaplan@...>
Date: Tue, 4 Mar 2008 21:50:44 -0500
To: "speermint@..." <speermint@...>
Subject: [Speermint] Comments on section-4 of
draft-ietf-speermint-architecture-05

------ Forwarded Message
From: Hadriel Kaplan <HKaplan@...>
Date: Tue, 4 Mar 2008 22:59:27 -0500

I-D ACTION:draft-ietf-speermint-architecture-06.txt

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Session PEERing for Multimedia INTerconnect Working Group of the IETF.

	Title		: SPEERMINT Peering Architecture
	Author(s)	: R. Penno
	Filename	: draft-ietf-speermint-architecture-06.txt
	Pages		: 21
	Date		: 2008-5-2
	
This document defines the SPEERMINT peering architecture, its  
  functional components and peering interface functions. It also 
  describes the steps taken to establish a session between two peering   
  domains in the context of the functions defined.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-speermint-architecture-06.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
Speermint mailing list
Speermint@...

Re: Some words on the federation concept

Dan,

We had discussed this way back at the beginning of Speermint and this is
consistent with that.

My assumption was silence was consent.

Mike

> -----Original Message-----
> From: speermint-bounces@... 
> [mailto:speermint-bounces@...] On Behalf Of Dan York
> Sent: Friday, May 02, 2008 5:30 AM
> To: Otmar Lendl
> Cc: speermint@...
> Subject: Re: [Speermint] Some words on the federation concept
> 
> Going back through older email, I saw this note from Otmar 
> and (at least in my mail program) zero replies.  Did everyone 
> agree with Otmar or did everyone miss his message in the 
> chaos of being at IETF 71?
> 
> For what it's worth, Otmar's definition seems fine by me.
> 
> Dan
> 
> On Mar 13, 2008, at 12:45 PM, Otmar Lendl wrote:
> 
> >
> > At yesterday's session, someone (I forgot, who) voiced his 

Re: New version of architecture draft

Reinaldo,

The first of my comments in the message you refer to below does not seem
to have been taken into account. Let me express it a different way. We
could have layer 5 peering between an enterprise or service provider
attached to the public Internet and an enterprise or service provider
attached to a private IP network. This possibility does not seem to be
acknowledged in section 2. Figure 1 quite rightly says that layer 3
peering between a public Internet and a private IP network is out of
scope, but I don't think layer 5 peering that happens to operate across
that same layer 3 peering point is out of scope.

John

> -----Original Message-----
> From: speermint-bounces@... 
> [mailto:speermint-bounces@...] On Behalf Of Reinaldo Penno
> Sent: 02 May 2008 17:18
> To: speermint@...
> Subject: [Speermint] New version of architecture draft
> 
> Hello,
> 
> I just submitted a new version (06) of the architecture draft 
> that should
> appear shortly. It hopefully addresses all comments made to 
> the list and at
> the IETF. It also incorporate feedback from other authors.
> 
> Email headers below for reference to the comments made to the list:

Re: New version of architecture draft

_______________________________________________
Speermint mailing list
Speermint@...
https://www.ietf.org/mailman/listinfo/speermint

Re: New version of architecture draft

_______________________________________________
Speermint mailing list
Speermint@...
https://www.ietf.org/mailman/listinfo/speermint

I-D Action:draft-ietf-speermint-voip-consolidated-usecases-07.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session PEERing for Multimedia INTerconnect Working Group of the IETF.

	Title           : VoIP SIP Peering Use Cases
	Author(s)       : A. Uzelac, Y. Lee
	Filename        : draft-ietf-speermint-voip-consolidated-usecases-07.txt
	Pages           : 26
	Date            : 2008-05-08

This document depicts many common VoIP use case for SIP Peering.
These use cases are categorized into static and on-demand, and then
further sub-categorized into direct and indirect.  These use cases
are not an exhaustive set, but rather the most common use cases
deployed today.  This document captures them to provide a reference.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-speermint-voip-consolidated-usecases-07.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
I-D-Announce mailing list
I-D-Announce <at> ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Direction of flows draft

Hello,

Now that we have newer version or architecture and use cases we need to look
at the direction and goals of the flows draft. Before actually talking about
what tasks could be done it would be good to hear from the list what are
their opinions on the draft. A few thoughts:

1 - Many of the flows are present on the use-cases draft. They are not in
"timeline" graphic format but there are messages, players, etc

2 - Many of the flows in the draft are already covered in other SIP drafts,
except for B2BUA/SBC flows.

3 - Given what I said above, it would be good to hear opinions if the draft
should be pursued further and in which format. One format could be to get
the use-cases examples and put them in timeline graphic format using SIP
nomenclature and/or speermint nomenclature. There are other possibilities.

4 - If people think we should pursue this further I would like to ask for
volunteers to help me edit the draft.

Let me know

Thanks,

Reinaldo

Re: Speermint Digest, Vol 29, Issue 4

----- Oorspronkelijk bericht -----
Van: speermint-request@...
Verzonden: vrijdag 9 mei 2008 21:00
Aan: speermint@...
Onderwerp: Speermint Digest, Vol 29, Issue 4

Send Speermint mailing list submissions to
	speermint@...

To subscribe or unsubscribe via the World Wide Web, visit
	https://www.ietf.org/mailman/listinfo/speermint
or, via email, send a message with subject or body 'help' to
	speermint-request@...

You can reach the person managing the list at
	speermint-owner@...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Speermint digest..."

Today's Topics:

   1. I-D
      Action:draft-ietf-speermint-voip-consolidated-usecases-07.txt
      (Internet-Drafts@...)

----------------------------------------------------------------------

Message: 1
Date: Thu,  8 May 2008 17:00:01 -0700 (PDT)

[Het originele bericht is niet volledig opgenomen]