[address-policy-wg] 2006-04 Draft Document will be produced (Contact e-mail Address Requirements)
- Previous message (by thread): [address-policy-wg] 2006-04 Draft Document will be produced (Contact e-mail Address Requirements)
- Next message (by thread): [address-policy-wg] 2006-04 Draft Document will be produced (Contact e-mail Address Requirements)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Denis Walker
denis at ripe.net
Tue Sep 26 18:45:29 CEST 2006
Wilfried Woeber, UniVie/ACOnet wrote: > From a technical & security point of view I like your proposal :-) > But... > > Jørgen Hovland wrote: > > >> Then I guess nobody will object when I put the following in my RIPE handle in order to be compliant with the new policy: >> >> e-mail: U2FsdGVkX19DjGgCGGBqHru1mllYpl+qhZZZycdQg9F42g== >> remarks: please decode my email address with base64 >> remarks: then decrypt it with AES-256-OFB using key jorgen >> remarks: then read from right to left >> remarks: In the subject you must put the name of the current day >> >> Or perhaps I should just use some javascript code instead? Or Haskell.. >> >> >> j >> > > ... quoting from $ whois -v person > > e-mail > > The e-mail address of a person, role, organisation or irt team. > This attribute is filtered from the default whois output when at > least one of the objects returned by the query contains an > abuse-mailbox attribute. > > An e-mail address as defined in RFC 2822. > > > I wonder if you approach is coverd by RFC 2822 :-) > sorry guys....you will not get past the parser with this one :) cheers denis > Wilfried. > >
- Previous message (by thread): [address-policy-wg] 2006-04 Draft Document will be produced (Contact e-mail Address Requirements)
- Next message (by thread): [address-policy-wg] 2006-04 Draft Document will be produced (Contact e-mail Address Requirements)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]