This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] 2015-04 New Version and Impact Analysis Published (RIPE Resource Transfer Policies)
- Previous message (by thread): [address-policy-wg] 2015-04 New Version and Impact Analysis Published (RIPE Resource Transfer Policies)
- Next message (by thread): [address-policy-wg] 2015-04 New Version and Impact Analysis Published (RIPE Resource Transfer Policies)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Mon Oct 24 19:22:05 CEST 2016
Hi Ciprian, > Actually there were cases where we did like that, being put as a contact for the LIR. I don't think this should be the solution as it doesn't seem adequate at least. There were also cases where we would have to "speak" on behalf of both parties so it would be awkward if not unprofessional to be a contact person for both sides. This sentence does not parse. You have to speak on behalf of parties but you cannot be a contact person for them? That doesn't make sense. If you feel that is awkward or unprofessional to speak on behalf of both then don't. Get a separate broker that represents the other party. But in what you wrote above you contradict yourself. > From our experience the need is just to "translate" (figurative and not) the messages between NCC and LIRs. It is a situation we meet often and I think it should be addressed in a clear procedural way. I don't agree with using tricks. This is not a trick. If you can speak on behalf of an LIR then you are a contact and should be registered as such. Cheers, Sander -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2084 bytes Desc: not available URL: </ripe/mail/archives/address-policy-wg/attachments/20161024/4d44c541/attachment.p7s>
- Previous message (by thread): [address-policy-wg] 2015-04 New Version and Impact Analysis Published (RIPE Resource Transfer Policies)
- Next message (by thread): [address-policy-wg] 2015-04 New Version and Impact Analysis Published (RIPE Resource Transfer Policies)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]