Dear all,
I would like to confirm this: As already pointed out by Bruno in 
http://www.ietf.org/mail-archive/web/int-area/current/msg03904.html there is 
the emergency call use case at ETSI and beside that there are application 
proposals within WGs SFC, TCPM, etc. beside other drafts which refer to RFC 
6967.

And although I might repeat again what has been stated many times: Intended 
goal is and should be to find a solution to fulfil dedicated and real use cases 
demands - respecting privacy, reducing vulnerability, strengthening protection 
against misuse as mentioned in BCP188, and so on ...

Best regards
Dirk 

-----Original Message-----
From: Int-area [mailto:int-area-boun...@ietf.org] On Behalf Of joel jaeggli
Sent: Montag, 9. Juni 2014 19:16
To: Stephen Farrell; Brandon Williams; Dan Wing
Cc: ietf-privacy@ietf.org; Internet Area
Subject: Re: [Int-area] [ietf-privacy] NAT Reveal / Host Identifiers

On 6/9/14, 7:01 AM, Stephen Farrell wrote:
> 
> 
> On 09/06/14 14:46, Brandon Williams wrote:
>>
>> Would you please indicate where the draft proposes a new identifier? 
>> If you are seeing a proposal for protocol changes somewhere in the 
>> draft, editing work is required in order to either clarify or excise 
>> the associated text.

There are 6 citations of

http://tools.ietf.org/html/rfc6967

the document doesn't exist in a vacuum where somehow how to do it has fallen 
off the table.

given the repeated asertion that this work is useful because of external 
requests (etsi) and that request is in fact tied closely to a particular method 
it is relatively strait forward to conflate the discussion of scenarios and 
methods.

> Fair enough that its an assumption of mine that adding some kind of 
> identifier is required to meet the (no-longer mis-stated:-) 
> requirements for these use-cases. But I think that is logically 
> required, and its valid to draw obvious conclusions and its also 
> invalid to ignore obvious conclusions.

> S.
> 
> _______________________________________________
> Int-area mailing list
> int-a...@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
> 


_______________________________________________
ietf-privacy mailing list
ietf-privacy@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-privacy

Reply via email to