Re: [sipcore] New Version Notification for draft-winterbottom-sipcore-locparam-02.txt

Went back to the RFC you are updating. The security considerations there are very much out of date with
current IETF practise in my opinion. If you update 6442, the security section would benefit from an update.

Referring to S/MIME (not really implemented much) and SIPS: (which is totally out-of-date) is not acceptable
any more. 

/O

> On 26 Oct 2017, at 15:09, Olle E. Johansson <oej@edvina.net> wrote:
> 
> Some quick comments to version -02:
> 
> in section 4, you refer to “other-loc-src” as a token. That’s not clearly specified. WIll there be a registry for “tokens”?
> I am afraid that this is an opening for private tokens that hinders interoperability.
> 
> In “Privacy considerations” - should you not discuss what happens with my privacy if an entity in the network,
> but not my phone, adds a location?
> 
> In “security considerations” there’s a discussion about a “trusted network” - but that is not defined. What is
> a trusted network? There’s no mention on how to apply trust, privacy, confidentiality.
> 
> There is a typo as well: "when passed to an other domain.”  
> s/an other/another/
> 
> Cheers,
> /O
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore