Re: [Sipping] FW: New Versiondraft-vanelburg-sipping-private-network-indication-01

["Hans Erik van Elburg" <[e-mail]>]

Hi Peter,

Thanks for reading the draft.

On 7.2.1:
Breakin can happen inside the public network. But I think we need to add
some extra information here saying that the indication only needs to be
added if the next hop or sip trunk send to does not implicitly mean that
the traffic is private.

On 7.2.2:
To be able to apply the special processing behaviours you have to
understand the extension. So you must support the extension. The special
processing behaviour are dependent on the specific business agreements
and regulatory requirements.

PL> - I propose to add that in case the indication is received from a
entitiy that is not trusted, then the Proxy MUST remove the indication
I think this is covered by 7.2.3, do you think that needs to be
clarified?

on 7.2.3:
The traffic should not be delivered to a user outside the enterprise
with an indicator. Because effectively the traffic has left the private
network (it is public network traffic). Do you think that such would be
clarified by having descriptive text elsewhere in the draft describing
breakout and breakin functions?

Best Regards,
/Hans Erik

-----Original Message-----
From: Leis, Peter (NSN - DE/Muenich) [mailto:[e-mail]] 
Sent: Tuesday, February 26, 2008 9:48 AM
To: [e-mail]
Cc: Hans Erik van Elburg
Subject: RE: [Sipping] FW: New
Versiondraft-vanelburg-sipping-private-network-indication-01


 Hans Erik

some comments

7.2.1
I don't understand why incoming public traffic to a corporate needs to
be marked as Private. I thought the "private" indication is only usefull
in public networks.

7.2.2
- "MUST support" this extension is rather vague. What is the real
requirement here in terms of protocol usage? Are there any procedures
expected to happen in the proxy?

- I propose to add that in case the indication is received from a
entitiy that is not trusted, then the Proxy MUST remove the indication

7.2.3
what is meant with "converting private traffic to public traffic"?  Is
forwarding a request that contains the new indication towards a user
(not beloinging to any corporate) also regarded as "converting private
traffic to public traffic"?


Peter

> -----Original Message-----
> From: [e-mail]
> [mailto:[e-mail]] On Behalf Of ext Hans Erik van 
> Elburg
> Sent: Saturday, February 23, 2008 1:39 AM
> To: [e-mail]
> Subject: [Sipping] FW: New
> Versiondraft-vanelburg-sipping-private-network-indication-01
> 
> 
> A new version of I-D,
> draft-vanelburg-sipping-private-network-indication-01.txt has been 
> successfuly submitted.
> 
> http://tools.ietf.org/html/draft-vanelburg-sipping-private-net
> work-indic
> ation-01
> 
> Revision Information
> - Added a solution based on a new header.  
> - Added Overview, Behaviour and Header Definition sections.  
> - Updated the trust domain definition.  Improved some of the existing 
> text
>   based on received comments.
> 
> Filename:	 draft-vanelburg-sipping-private-network-indication
> Revision:	 01
> Title:		 Requirements for explicit private 
> network indication
> Creation_date:	 2008-02-22
> WG ID:		 Independent Submission
> Number_of_pages: 15
> 
> Abstract:
> This document describes why a private network indication is needed.
> A private network indication allows other nodes in a network to treat 
> private network traffic to a different set of rules then public 
> network traffic.  The indication also distinguishes one private 
> network from another private network.
>  
> 
> 
> Best Regards,
> /Hans Erik
> 
> 
> 
> _______________________________________________
> Sipping mailing list  http://www.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP Use 
> [e-mail] for questions on current sip Use 
> [e-mail] for new developments of core SIP
> 
_______________________________________________
Sipping mailing list  http://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [e-mail] for questions on current sip
Use [e-mail] for new developments of core SIP