On Thu, Aug 21, 2014 at 3:51 PM, Kathleen Moriarty < [email protected]> wrote:
> > > > On Thu, Aug 21, 2014 at 3:49 PM, Stephen Farrell < > [email protected]> wrote: > >> >> Hiya, >> >> On 21/08/14 20:44, Kathleen Moriarty wrote: >> > OK, this isn't my area of expertise, so I didn't read it the same way in >> > that information was limited to requests of public data. >> > >> >> Nothing really to do with IESG processing of this but I'm >> curious... >> >> Is the full DB information really considered public? > > > I'm glad it wasn't just me ;-) Maybe stating that explicitly would be > good. > > My >> impression was rather that trying to extract the full DB >> of information via repeated queries would be frowned upon. >> > Just to be clear - As I understand it now, the database may have sensitive information, but the interface via PAWS only allows access to data that is not sensitive. If you can query it, it is public. If you have database access or other extensions are written, then it could be possible to get access to sensitive data. > >> S. >> > > > > -- > > Best regards, > Kathleen > -- Best regards, Kathleen
_______________________________________________ paws mailing list [email protected] https://www.ietf.org/mailman/listinfo/paws
