RE: RE: NCS Signaling MIB SC Objects

"Eugene Nechamkin" <[email protected]>
Newsgroups gmane.ietf.ipcdn
Message-ID <24CDBA67F085904999751B3C4F9E8C0BE2D142@NT-RMNA-0740.brcm.ad.broadcom.com>
Hi Thomas,

> We as an MSO clearly see more (security) problems than benefits with this
> approach. 
Could you be more specific on particular (security) concerns you see as the potential problems for SC Objects usage and implementation ?

Thanks,

Eugene Nechamkin

Broadcom Corp,
ph: (604) 233-8500



-----Original Message-----
From: [email protected] [mailto:[email protected]]On Behalf Of
Thomas Anders
Sent: Wednesday, April 07, 2004 6:17 AM
To: [email protected]
Subject: Re: [ipcdn] RE: NCS Signaling MIB SC Objects


Hi all,

since part of this discussion is related to MSOs, we'd like to speak up.

Wim>   It is clearly not the intention of the PacketCable
Wim>   specification that any DSA for a SCN will always succeed,
JFM>
JFM> That is a question of MSO policy authorization and is left for vendor 
differentiation.
[...]
Wim>   this would be a very easy theft-of-service scenario
JFM>
JFM> An operator would have to allow this.
[...]
Wim>   just stating that any SCN can be allowed without authorization
Wim>   opens up a security hole
JFM>
JFM> Operator decision.

We as an MSO clearly see more (security) problems than benefits with this
approach. We can hardly imagine "vendor differentiation" offering any
acceptable solution here. Even worse, much like Wim, we don't think it
fits with the current specs.


Best regards,
Thomas

-- 
Thomas Anders (thomas.anders at blue-cable.de)
Bosch Breitbandnetze GmbH, Berlin, Germany


_______________________________________________
IPCDN mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ipcdn
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.