ma@dde.dk (michael andersen) (01/24/91)
We are rigth now working on an RFC-987 gateway, but we do have a problem with the 822.msg-id -> P2.IPMessageID mapping. The problem is how to map an 822.msg-id into an OR-Name. The RFC-987 just says "822.addr-spec is mapped to P2.IPMessageID.ORName as defined above" but what do we do when our 822.msg-id don't contain a normal RFC-822 address. F.ex. how do we map the 822.msg.id below into an P2.IPMessageID ? Message-Id: <9006121212.AA12456@Kurt.dde.dk> ------------------------------------------------------------------------ Michael Andersen email: ma@dde.dk Dansk Data Elektronik A/S Fax: +45 42 84 52 20 199, Herlev Hovedgade Voice: +45 42 84 50 11 DK - 2730 Herlev, Denmark ------------------------------------------------------------------------
S.Kille@cs.ucl.ac.UK (Steve Kille) (01/24/91)
There were some fundamental problems with the 987 mapping of message IDs. Have a look at RFC 1148, which fixes this up. Steve
pv@eng.sun.COM (Peter Vanderbilt) (01/25/91)
> F.ex. how do we map the 822.msg.id below into an P2.IPMessageID ? > > Message-Id: <9006121212.AA12456@Kurt.dde.dk> The IP Message Id ends up with an ORName in the DDA form: /DD.RFC-822=9006121212.AA12456(a)Kurt.dde.dk/.../ This has been known to cause problems with other implementations, especially those compare IPMessageIds for equality but don't compare the DDA fields of the ORNames. Pete