Email Detail

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/GQN66W4DHOQJYEXDIZCCLWG3525EQ6AV/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "GQN66W4DHOQJYEXDIZCCLWG3525EQ6AV",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/GQN66W4DHOQJYEXDIZCCLWG3525EQ6AV/?format=api",
    "sender": {
        "address": "wb4gcs (a) amsat.org",
        "mailman_id": "87014499e012476c8198fad186f7f963",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/87014499e012476c8198fad186f7f963/emails/?format=api"
    },
    "sender_name": "Jim Sanford",
    "subject": "[eagle]  Where we're heading for bands and services",
    "date": "2006-09-25T00:36:40Z",
    "parent": null,
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/2XQJG5WZJIYBQKGF4LAA5OXBMPHKL2FQ/?format=api",
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/QLBDEFHEGVMCP76F3RCHYHFHLRYTHM7B/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Team:\n \n\nThe Eagle Chief Technology Officer (W2GPS), the AMSAT VP Engineering \n\n(N4HY) and I met (electronically) to discuss the Eagle payload complement.\n\n \n\nWe have decided the following should be our recommendation to the board of \n\ndirectors of AMSAT for their ratification.  This is what will be presented to the BoD:\n\n \n\n1.  Services to be provided, as defined at the San Diego meeting et seq:\n\n        Class 0 is linear transponder users\n\n        Class 1 is SMS text message service users\n\n        Class 2 is weak signal voice grade digital channel\n\n        Class 3 is strong signal, large antenna, higher bandwidth signal (think \n\ncompressed full motion video)\n\n \n\n2.  Primary class 0 payload:  U/V with a design goal that it be usable over \n\n75% of the orbit.\n\n \n\n3.  Primary class 1 payload:  U/V for the reasons discussed at San Diego.\n\n \n\n3.  Primary Class 2 and 3 ACP payload:  S2/C usable over 75% of the orbit.  This \n\ncoverage to be accomplished by using electronically de-spun phased arrays on S2 and C.  \n\nAt San Diego, we discussed S2 vs. S1.  S2 was technically superior, but other issues \n\ncaused us to shy away from it.  Upon reflection, the leadership has decided to proceed \ndown the technically superior path, S2 uplink.\n\n \n\n4.  Secondary Class 0 payload:  L/S1  -if and when the power budget and \n\nantenna pointing (fixed, nadir-pointing array) can support.  We recognize that it may not be usable \n\nin many areas due to elevated noise floor resulting from 802.xx devices, as discussed in San\n\nDiego and documented in measurements and analysis.  \n\nNO PERFORMANCE LEVEL IS TO BE PROMISED.\n\n \n\n5.  Secondary ACP Class 2 uplink:  A separate L receiver feeding same DSP and C-band \n\ndownlink when fixed nadir-pointing antenna array supports.   This second receiver will share \n\nthe L-band LNA and antenna with the L/S1 Class 0 payload.\n\nThe greater level of service for S2 users should encourage people who can to use S2 rather than L.  \n\nNO PERFORMANCE LEVEL IS TO BE PROMISED.\n\n \n\n6.  Use of all secondary payloads will be subject to acceptable costs in power, heat, and/or mass,\n\nas assessed by analysis or testing.  They are to be turned off if regulatory constraints are \n\nimposed post launch.  They will not be flown at all if shown to be not feasible through \n\nanalysis or testing.\n\n \n\nThis is what I will present to the board at Symposium for their concurrence.  Please contain this \ndiscussion within the Eagle team until the Board makes a decision.\n\n \n\nI request your comments within the next 48 hours so that I can finish the budget tonight and begin \n\ncrafting my presentation to the board and my follow-on presentation at Symposium.  We need to bring \nthis to closure so that we can present decisions at Symposium, and move out smartly from there.  Thanks.\n\n \n\nVery 73,\n\nJim\n\[email protected] <mailto:[email protected]>\n\nUNQUOTE\n\n\n\n",
    "attachments": [
        {
            "email": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/GQN66W4DHOQJYEXDIZCCLWG3525EQ6AV/?format=api",
            "counter": 2,
            "name": "attachment.html",
            "content_type": "text/html",
            "encoding": "iso-8859-1",
            "size": 11899,
            "download": "https://mailman.amsat.org/hyperkitty/list/[email protected]/message/GQN66W4DHOQJYEXDIZCCLWG3525EQ6AV/attachment/2/attachment.html"
        }
    ]
}